U Ministry Utility
50“"Application and site development is still a complex process for churches and religious organizations." AND "A RESTful API of the Holy…”
source unavailable
omarciovsena/abibliadigital
A RESTful API for Bible
Trust Score
33.0
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“"Application and site development is still a complex process for churches and religious organizations." AND "A RESTful API of the Holy…”
source unavailable
M Maturity
0“"Site e APIs desativados desde 01/08/2026." AND latest commit message: "end-of-the-line (#552)" dated 2026-07-25 (latest_commit, README) —…”
source unavailable
35.0 → 35.0 (+0.0 over window)
ranked #3 of 6 in G1 (▲1 vs previous snapshot)
omarciovsena/abibliadigital looks like a candidate for apis & web services; CRITICAL: Project is explicitly deactivated — "Site e APIs desativados desde 01/08/2026" (README). Latest commit "end-of-the-line (#552)" confirms shutdown. This caps M at 0 despite recent commit activity.
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 omarciovsena/abibliadigital: 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 omarciovsena/abibliadigital (https://refinry.dev) and help me assess it for using omarciovsena/abibliadigital for apis & web services 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: "license.spdx_id": "BSD-2-Clause" (api.repos) — permissive license. Security: "unfetched: security posture" — no SECURITY.md…”
source unavailable
A Ease of Adoption
50dev 50 · volunteer 25
“"Setup using Docker" section exists and "If you do not want to install Mongo, Redis, Node and Yarn, follow these steps." (README) — but…”
source unavailable
C Community Trust
50“"stargazers_count": 1003, "forks_count": 166 (api.repos) AND Discord community link "" (README) — small real community with external…”
source
I AI-Agent Integrability
50“"Documentation" link to "DOCUMENTATION.md" (README) AND "A RESTful API for Bible" (api.repos) — accurate README with install/use sections…”
source unavailable