U Ministry Utility
50“README: 'Source code for [colabor.ing](' and TODO: 'Collect amount expected to pay so can issue receipts' — purpose-built for…”
source
gracious-tech/colabor
No repository description supplied.
Trust Score
26.8
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: 'Source code for [colabor.ing](' and TODO: 'Collect amount expected to pay so can issue receipts' — purpose-built for…”
source
M Maturity
25“api.repos: pushed_at 2025-11-23 (within 12 months of fetch 2026-09-28); latest_commit: "fix contacts bug" 2025-11-23; api.releases: no…”
28.8 → 28.8 (+0.0 over window)
ranked #6 of 7 in G9 (▼4 vs previous snapshot)
gracious-tech/colabor looks like a candidate for design, templates & themes; No tagged release; single contributor; no security policy; no build/run docs; no Dockerfile or demo signals in pack (unfetched: Dockerfile/registry/demo).
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 gracious-tech/colabor: 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 gracious-tech/colabor (https://refinry.dev) and help me assess it for using gracious-tech/colabor for design, templates & themes 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: api.repos license.spdx_id "MIT-0" (permissive). Security: security_md present false (no security policy); no OSV vulns but no…”
source unavailable
A Ease of Adoption
25dev 25 · volunteer 0
“README: 'Source code for [colabor.ing](' — no install/build docs, no Dockerfile, no quickstart; developer has only source code and no setup…”
source
C Community Trust
0“api.repos: stargazers_count 3, forks_count 0; api.contributors: top empty; no external contributors or third-party mentions in pack.”
source unavailable
I AI-Agent Integrability
25“README: 'Source code for [colabor.ing](' — sparse README with only a TODO list and legal notes; no API description, no machine-readable…”
source