U Ministry Utility
25“api.repos: "Simplify your church operations with an open-source ERP for document generation, finance tracking, attendance, and more." —…”
source unavailable
elezerk-19/church-erp
Simplify your church operations with an open-source ERP for document generation, finance tracking, attendance, and more.
Trust Score
29.2
Last full review 2026-09-29 · Trust Score decays −2 points per month without a fresh review (never below 20)
U Ministry Utility
25“api.repos: "Simplify your church operations with an open-source ERP for document generation, finance tracking, attendance, and more." —…”
source unavailable
M Maturity
25“api.repos created 2026-07-12, pushed 2026-07-12 (single day of activity); api.releases: "no tagged release found"; latest_commit: "feat…”
source unavailable
31.2 → 31.2 (+0.0 over window)
ranked #2 of 4 in M1
elezerk-19/church-erp looks like a candidate for church management (chms); README describes a stock Nuxt UI starter template, contradicting the church-ERP description — strong smell of scaffold/rename; ministry functionality unverified.
Use it with
Selected: Gloo AI Studio
Tool names and logos belong to their owners; shown so you can pick your own client. Not affiliated.
Step 1 — Connect Refinry once (prompt only)
Gloo AI Studio does not document external MCP server setup. Use this prompt with the copied Refinry research brief in Studio.
https://studio.ai.gloo.com/I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s plain-language agent feed — https://refinry.dev/docs.md — then help me evaluate elezerk-19/church-erp: summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.
Some clients need manual setup. Follow the plain-language steps on the Docs page.
Step 2 — Plan your first step
Tell the AI what you want to do; edit this to match your situation.
I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s public review of elezerk-19/church-erp (https://refinry.dev) and help me assess it for using elezerk-19/church-erp for church management (chms) in my ministry. Summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites, separating reviewed evidence from what still needs verification. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.
Prefer a hand-off that works without a connection? Copy the research brief: every reviewed fact, all caution flags, and a feasibility-only first assignment.
S Security / License
50license 75 · security 50
“License: api.repos "license.spdx_id": "MIT" (permissive) — 75. Security: security "osv_vulns": [] and "security_md": {"present": false}; no…”
source unavailable
A Ease of Adoption
50dev 50 · volunteer 25
“README: "Make sure to install the dependencies: pnpm install" and "pnpm dev / pnpm build" — standard tooling for a developer (50); but…”
source unavailable
C Community Trust
0“api.repos: "stargazers_count": 0, "forks_count": 0, "open_issues_count": 0; api.contributors: "top": [] — zero external-witness evidence.”
source unavailable
I AI-Agent Integrability
25“README: "# Nuxt Starter Template ... Use this template to get started with Nuxt UI quickly." — sparse, parseable, but entirely wrong for…”
source unavailable