U Ministry Utility
25“api.repos.description: "CHURCH MANAGEMENT SYSTEM" — but README excerpt contains zero ministry functionality: "# Welcome to the Node.js…”
source unavailable
eruditewbt/local_church_management
CHURCH MANAGEMENT SYSTEM
Trust Score
24.2
Last full review 2026-09-28 · Trust Score decays −2 points per month without a fresh review (never below 20)
U Ministry Utility
25“api.repos.description: "CHURCH MANAGEMENT SYSTEM" — but README excerpt contains zero ministry functionality: "# Welcome to the Node.js…”
source unavailable
M Maturity
25“api.contributors: single contributor "eruditewbt" with 3 contributions; api.releases: no tagged release; latest_commit 2025-12-24 (within…”
source unavailable
26.2 → 26.2 (+0.0 over window)
ranked #3 of 4 in M1
eruditewbt/local_church_management looks like a candidate for church management (chms); Ministry category M1 assigned generously from description "CHURCH MANAGEMENT SYSTEM"; README provides no ministry-functional evidence, so U stays at generic-tool anchor.
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 eruditewbt/local_church_management: 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 eruditewbt/local_church_management (https://refinry.dev) and help me assess it for using eruditewbt/local_church_management 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
“api.repos.license.spdx_id: "MIT" (permissive, no dep-scan/NOTICE evidence → 75); security: "osv_vulns": [] clean, but…”
source unavailable
A Ease of Adoption
0dev 25 · volunteer 0
“README: "to start app use setup.bat / setup.sh" plus "$ npm install --build-from-source --sqlite=sqlcipher-4.10.0" and "netlify dev" —…”
source unavailable
C Community Trust
25“api.contributors: only "eruditewbt"; "forks_count": 0; stars (61) are at most one weak input; no external issue reporters or third-party…”
source unavailable
I AI-Agent Integrability
25“README excerpt: sparse, parseable steps ("npm install", "npm start", "npm run key") but titled "Node.js Database App" — inaccurate to repo…”
source unavailable