U Ministry Utility
25“README: "This is the an OIDC App for Nextcloud. This application allows to use your Nextcloud Login at other services supporting OpenID…”
source unavailable
H2CK/oidc
OpenID Connect App for Nextcloud
Trust Score
36.8
Last full review 2026-10-01 · Trust Score decays −2 points per month without a fresh review (never below 20)
security cap applied — score capped at 45U Ministry Utility
25“README: "This is the an OIDC App for Nextcloud. This application allows to use your Nextcloud Login at other services supporting OpenID…”
source unavailable
M Maturity
50“api.releases: "latest tag 2.4.1 published 2026-09-30"; latest_commit 2026-10-01; api.contributors top: nextcloud-bot, H2CK, dependabot[bot]…”
source unavailable
38.8 → 38.8 (+0.0 over window)
ranked #7 of 11 in G10 (▼1 vs previous snapshot)
H2CK/oidc looks like a candidate for libraries & frameworks (sdks); AGPL-3.0 identified via api.repos; tags list lacks an AGPL/copyleft tag, license-ambiguous fired generously pending human review of redistribution implications.
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 H2CK/oidc: 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 H2CK/oidc (https://refinry.dev) and help me assess it for using H2CK/oidc 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 25 · security 75
“api.repos.license.spdx_id "AGPL-3.0" (restrictive for SaaS/redistribution); security: osv_vulns [], security_md present, dependabot among…”
source unavailable
A Ease of Adoption
50dev 50 · volunteer 25
“README: "Full documentation can be found at: User Documentation ... Developer Documentation" (wiki links) and "Administration of clients…”
source unavailable
C Community Trust
50“api.repos: 134 stars, 18 forks; dependabot activity; no church/ministry users visible in pack — small real reliance signals only.”
source unavailable
I AI-Agent Integrability
50“README accurately lists API surface: "Discovery & WebFinger endpoint provided", "Token Introspection (RFC 7662)", SPDX license via…”
source unavailable