U Ministry Utility
50“README: "This project exposes an API at `" and "Download the json file that hold the data for every hymn" with a hymn index ("It is well…”
source
marvinjude/gospel-hymns
Gospel Hymns and Songs(GHS) for developers
Trust Score
24.2
Last full review 2026-09-28 · Trust Score decays −2 points per month without a fresh review (never below 20)
security cap applied — score capped at 45U Ministry Utility
50“README: "This project exposes an API at `" and "Download the json file that hold the data for every hymn" with a hymn index ("It is well…”
source
M Maturity
25“api.releases: "no tagged release found"; latest_commit 2023-03-29 (pushed_at 2023-07-18), >12 months before 2026-09-28 fetch; contributors…”
26.2 → 26.2 (+0.0 over window)
ranked #10 of 11 in M9
marvinjude/gospel-hymns looks like a candidate for ministry data & theology resources; No LICENSE file detectable (spdx_id null) → license-ambiguous; S forced to 0 fail-closed despite clean OSV. This alone blocks adoption until a license is added.
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 marvinjude/gospel-hymns: 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 marvinjude/gospel-hymns (https://refinry.dev) and help me assess it for using marvinjude/gospel-hymns for ministry data & theology resources 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
0license 0 · security 25
“api.repos.license.spdx_id: null — no detectable license; security.md "present": false; osv_vulns: []. Fail-closed: S = min(0, 25) = 0.”
source unavailable
A Ease of Adoption
25dev 50 · volunteer 25
“README offers "Download hymns JSON" and a live demo URL, but no install/config/setup docs in pack; adoption pack: "unfetched…”
source unavailable
C Community Trust
25“39 stars, 12 forks; contributors limited to "marvinjude" and "dependabot[bot]"; no external issue reporters or third-party mentions in…”
source unavailable
I AI-Agent Integrability
25“README documents API base URL and example endpoint ("/api/v1/hymn/26") — parseable, but no license identifiable (spdx null), no…”
source unavailable