U Ministry Utility
50“"The Open Scriptures Hebrew Bible (OSHB) is a project to analyze the Hebrew Bible by lemma and morphology. The project is marked up in OSIS…”
source unavailable
openscriptures/morphhb
Open Scriptures Hebrew Bible
Trust Score
39.2
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“"The Open Scriptures Hebrew Bible (OSHB) is a project to analyze the Hebrew Bible by lemma and morphology. The project is marked up in OSIS…”
source unavailable
M Maturity
50“latest tag "v.2.2 published 2021-12-13T14:47:08Z" — api.releases; latest commit "2024-08-27T13:19:54Z" — latest_commit. Has a tagged…”
source unavailable
41.2 → 41.2 (+0.0 over window)
ranked #3 of 11 in M9
openscriptures/morphhb looks like a candidate for ministry data & theology resources; unfetched: contributors — contributor breakdown not in pack; M maturity capped at 50 due to inability to verify >=2 active contributors.
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 openscriptures/morphhb: 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 openscriptures/morphhb (https://refinry.dev) and help me assess it for using openscriptures/morphhb for ministry data & theology resources 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 50 · security 25
“License: "Lemma and morphology data are licensed under a Creative Commons Attribution 4.0 International license... The text of the WLC…”
source unavailable
A Ease of Adoption
25dev 50 · volunteer 25
“README describes project structure and data format but provides no install/run instructions, no Dockerfile, no dependency pinning, no…”
source unavailable
C Community Trust
50“"stargazers_count": 246, "forks_count": 83" — api.repos; latest commit references external collaborators: "Changes requested by Randall Tan…”
source unavailable
I AI-Agent Integrability
50“README accurately describes data structure: "Word tags each contain three attributes: lemma... morph... id" with examples. OSIS XML is a…”
source unavailable