U Ministry Utility
50“This project is a Typescript implementation of a Bible-passage reference parser (seeing `John 3:16`, for example, and both understanding…”
source unavailable
openbibleinfo/Bible-Passage-Reference-Parser
Typescript to identify and understand Bible references like "John 3:16."
Trust Score
38.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“This project is a Typescript implementation of a Bible-passage reference parser (seeing `John 3:16`, for example, and both understanding…”
source unavailable
M Maturity
25“api.repos: pushed_at 2026-07-31, open_issues_count 0, archived false. latest_commit message: "4.0.0 release." dated 2026-07-31. BUT…”
source unavailable
40.0 → 40.0 (+0.0 over window)
ranked #6 of 11 in G10 (▼1 vs previous snapshot)
openbibleinfo/Bible-Passage-Reference-Parser looks like a candidate for libraries & frameworks (sdks); unfetched: contributors — contributor breakdown not in pack; bus-factor cannot be assessed.
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 openbibleinfo/Bible-Passage-Reference-Parser: 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 openbibleinfo/Bible-Passage-Reference-Parser (https://refinry.dev) and help me assess it for using openbibleinfo/Bible-Passage-Reference-Parser for libraries & frameworks (sdks) 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
“api.repos: license.spdx_id MIT — permissive license. security: "unfetched: SECURITY.md/dependabot/CodeQL/OSV not in pack" — no security…”
source unavailable
A Ease of Adoption
50dev 50 · volunteer 25
“README: "npm i bible-passage-reference-parser" with clear Node and browser usage examples — developer-adoptable. But no Dockerfile, no GUI…”
source unavailable
C Community Trust
50“api.repos: stargazers_count 262, forks_count 72 — suggests small real community with substantive forks. README: "4.7 million real-world…”
source unavailable
I AI-Agent Integrability
50“README: accurate install/use sections, clear API surface ("bcv.parse(\"John 1\")"), consistent layout, SPDX-identifiable MIT license. No…”
source unavailable