U Ministry Utility
50“"The *compendium* is a collection of reformed documents, such as confessions and catechisms." (`56206_open_serve`.`readme`) — Directly…”
source unavailable
reformed-standards/compendium
No repository description supplied.
Trust Score
31.8
Last full review 2026-09-24 · Trust Score decays −2 points per month without a fresh review (never below 20)
security cap applied — score capped at 45U Ministry Utility
50“"The *compendium* is a collection of reformed documents, such as confessions and catechisms." (`56206_open_serve`.`readme`) — Directly…”
source unavailable
M Maturity
25“"no tagged release found" (api.releases); latest commit "Fix email address now that confessional.tech is defunct" dated 2026-09-21…”
source unavailable
33.8 → 33.8 (+0.0 over window)
ranked #6 of 11 in M9
reformed-standards/compendium looks like a candidate for ministry data & theology resources; unfetched: contributors — contributor breakdown not in pack; bus-factor cannot be assessed.
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 reformed-standards/compendium: 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 reformed-standards/compendium (https://refinry.dev) and help me assess it for using reformed-standards/compendium 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
25license 75 · security 25
“"license.spdx_id": "Apache-2.0" (api.repos) — permissive license. Security: unfetched: security posture (SECURITY.md/dependabot/CodeQL/OSV…”
source unavailable
A Ease of Adoption
25dev 50 · volunteer 25
“"Feel free to email us patches (team at reformedstandards.com), or open issues and pull requests on GitHub" (`56206_open_serve`.`readme`) —…”
source unavailable
C Community Trust
25“stargazers_count=36, forks_count=3 (api.repos); `56206_open_serve`.`readme` invites contributions but no external contributors or…”
source unavailable
I AI-Agent Integrability
50“`56206_open_serve`.`readme` lists structured document tree ("westminster / wcf / wlc / wsc") and SPDX-identifiable license (Apache-2.0)…”
source unavailable