U Ministry Utility
50“api.repos: "The monorepo for everything lets.church" — a church-branded platform (M5 media/streaming lane), and README shows an…”
source unavailable
LetsChurch/lets.church
The monorepo for everything lets.church
Trust Score
34.2
Last full review 2026-09-29 · Trust Score decays −2 points per month without a fresh review (never below 20)
U Ministry Utility
50“api.repos: "The monorepo for everything lets.church" — a church-branded platform (M5 media/streaming lane), and README shows an…”
source unavailable
M Maturity
25“Alive but fragile: latest_commit 2026-09-25 "fix(docker): temporarily bypass AMD AMA package feed"; but api.releases: "no tagged release…”
source unavailable
36.2 → 36.2 (+0.0 over window)
ranked #1 of 4 in M1
LetsChurch/lets.church looks like a candidate for church management (chms); No tagged release ever + single dominant contributor (knpwrs) — bus-factor and upgrade-path concerns.
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 LetsChurch/lets.church: 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 LetsChurch/lets.church (https://refinry.dev) and help me assess it for using LetsChurch/lets.church 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": "CC0-1.0" — public-domain dedication, effectively permissive, but "missing license scan of bundled…”
source unavailable
A Ease of Adoption
25dev 50 · volunteer 25
“README: "Copy `.envrc.local.example` to `.envrc.local`", "Run `just start` to start the `docker-compose` setup", "Run `just seed` to seed…”
source unavailable
C Community Trust
25“api.repos: "stargazers_count": 12, "forks_count": 1; api.contributors: single author {"login": "knpwrs", "contributions": 1876}. No…”
source unavailable
I AI-Agent Integrability
25“README excerpt is parseable and has a Setup section, but no described API/CLI surface, no OpenAPI/schema/CITATION signals (agent…”
source unavailable