U Ministry Utility
50“README: 'A digital prayer room experience, inspired by real life prayer rooms, the Prayroom app, and the Salt + Light app.' Purpose-built…”
source unavailable
cameronapak/be-still
A digital prayer room, connected via WebSockets
Trust Score
33.8
Last full review 2026-10-06 · Trust Score decays −2 points per month without a fresh review (never below 20)
U Ministry Utility
50“README: 'A digital prayer room experience, inspired by real life prayer rooms, the Prayroom app, and the Salt + Light app.' Purpose-built…”
source unavailable
M Maturity
0“latest_commit date '2024-11-10T14:48:35Z' vs pack fetch date 2026-09-29 (~22 months, no commits within 12 months); api.releases: 'no tagged…”
source unavailable
cameronapak/be-still looks like a candidate for prayer & discipleship; Repo effectively dormant: last push 2024-11-10, ~22 months before 2026-09-29 fetch; not archived but meets 'no activity for 12 months' dead/fragile criteria.
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 cameronapak/be-still: 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 cameronapak/be-still (https://refinry.dev) and help me assess it for using cameronapak/be-still for prayer & discipleship 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: README 'MIT No Attribution' full text — permissive, but no dep-license scan in pack. Security: security.osv_vulns '[]' (clean…”
source unavailable
A Ease of Adoption
25dev 50 · volunteer 25
“README has clear dev steps ('cp .env.example .env', 'npm run dev', Node 'v20.3.0 or higher') → developer ~50. But 'Prerequisites: A Groq…”
source unavailable
C Community Trust
25“api.repos: 4 stars, 1 fork, 0 open issues; api.contributors shows only 'cameronapak'. No external contributors or third-party mentions in…”
source unavailable
I AI-Agent Integrability
50“README accurate with structured sections (Local Development, Prerequisites, Contributing) and full license text embedded ('MIT No…”
source unavailable