U Ministry Utility
75“README: 'An open-source website builder for Catholic parishes... you edit your site in the Builder (a visual editor in your browser). No…”
source unavailable
ngwessels/opensource-church-websites
No repository description supplied.
Trust Score
48.8
Last full review 2026-10-06 · Trust Score decays −2 points per month without a fresh review (never below 20)
U Ministry Utility
75“README: 'An open-source website builder for Catholic parishes... you edit your site in the Builder (a visual editor in your browser). No…”
source unavailable
M Maturity
25“api.repos: created_at 2026-06-06, pushed_at 2026-09-30; api.releases: no tagged release found; api.contributors: two contributors…”
source unavailable
ngwessels/opensource-church-websites looks like a candidate for websites & digital presence; No tagged release; project is young (created 2026-06-06) with active commits (latest 2026-09-30).
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 ngwessels/opensource-church-websites: 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 ngwessels/opensource-church-websites (https://refinry.dev) and help me assess it for using ngwessels/opensource-church-websites for websites & digital presence 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; security: osv_vulns empty, security_md absent, no dependency-update tooling mentioned.”
source unavailable
A Ease of Adoption
50dev 50 · volunteer 50
“README: 'Most parishes can complete setup in one afternoon with a little help on DNS and the security-rules step.' Requires GitHub…”
source unavailable
C Community Trust
25“api.contributors: only ngwessels and cursoragent; stargazers 0, forks 0, open_issues 0; no external users or third-party mentions in pack.”
source unavailable
I AI-Agent Integrability
50“README: clear sections (What you can do, Before you start, Step 1—Step 2), MIT license identifiable via api.repos, described setup flow…”
source unavailable