# eclipse-xfsc/oid4-vci-authorization-bridge — health index 59/100 (Moderate)

> Inspection of the public repository eclipse-xfsc/oid4-vci-authorization-bridge by inspect.software. It holds a health index of 59 out of 100, placing it in the Moderate band. The index is a signal derived from publicly visible practice, not a warranty, a security audit, or an endorsement, and it is independent of payment.

- Repository: https://github.com/eclipse-xfsc/oid4-vci-authorization-bridge
- Report page: https://inspect.software/software/eclipse-xfsc/oid4-vci-authorization-bridge
- Full JSON report: https://inspect.software/api/repositories/eclipse-xfsc/oid4-vci-authorization-bridge/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/e/eclipse-xfsc/oid4-vci-authorization-bridge.svg
- Inspected: 2026-09-23
- Methodology: metrics 2.10.0, report schema 0.34.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 74/100 | Good |
| Community & Adoption | 17% | 45/100 | Weak |
| Sustainability & Governance | 23% | 46/100 | Weak |
| Engineering Quality | 19% | 70/100 | Good |
| Security | 16% | 46/100 | Weak |
| AI Readiness | 4% | 48/100 | Weak |

The weighted overall 56 is calibrated to 59 on the published index scale (record calibration 2026-08-02).

## Repository facts

| Field | Value |
|---|---|
| Description | The pre authorization provides the new grant type for the OID4VCI flow to support issuing operations with the pre authorization flow. This bridge can be later configured in the open id configuration under the type urn:ietf:params:oauth:grant-type:pre-authorized_code which is defined in the OID4VCI Spec |
| Classification | network-service, library |
| Primary language | Go |
| License | Apache-2.0 |
| Stars | 0 |
| Forks | 1 |
| Created | 2025-04-10 |
| Last push | 2026-09-11 |
| Latest release | v2.5.6 |
| Commits (last year) | 37 |
| Bus factor | 1 |
| Topics | golang, oauth2, oid4vci, vc, vp, pre-authorized-code, ocm-w-stack |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| go | github.com/eclipse-xfsc/oid4-vci-authorization-bridge/v2 | v2.5.6 | — |

## Vitality — 74/100 (Good)

Is the project alive — is code being written and are releases shipping? Weight: 21% of the overall index.

### Development activity — 57/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | partial | 28.8 / 36 | last push 12 days ago |
| Commit cadence | partial | 8.3 / 36 | 12/52 weeks with commits |
| Commit volume | partial | 14.2 / 18 | 37 commits in the last year |
| OpenSSF Scorecard: Maintained | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Release discipline — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 33 releases published |
| Release recency | met | 36 / 36 | latest release 12 days ago |
| Release cadence | met | 27 / 27 | a release every ~2.4 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Abandonment — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | last human commit 12 days ago |

## Community & Adoption — 45/100 (Weak)

Does the project have users, downloads, attention, and a welcoming setup for contributors? Weight: 17% of the overall index.

### Popularity & adoption — 4/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | not met | 0 / 60 | 0 stars |
| Forks | not met | 0 / 25 | 1 forks |
| Watchers | partial | 4.3 / 15 | 7 watchers |

### Community health — 92/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (Apache-2.0) |
| CONTRIBUTING guide | met | 18 / 18 | — |
| Code of conduct | met | 13.5 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | met | 6.3 / 6.3 | — |

## Sustainability & Governance — 46/100 (Weak)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 23% of the overall index.

### Maintainer resilience (bus factor) — 12/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | not met | 0 / 22.5 | top contributor authored 100% of commits |
| Contributor breadth | partial | 1.4 / 13.5 | 1 contributors |
| OpenSSF Scorecard: Contributors | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Issue & PR responsiveness — 34/100 (At Risk)

Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | excluded | 0 / 42 | no issues or no data |
| PR acceptance | partial | 1.5 / 30 | 1/20 decided PRs merged |
| Newcomer PR acceptance | met | 13 / 13 | 1/1 first-time contributors' PRs merged in 30d |
| OpenSSF Scorecard: Code-Review | excluded | 0 / 15 | OpenSSF Scorecard unavailable |

### Ownership & stewardship — 55/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 8.5 / 25 | 14 followers of eclipse-xfsc |
| Track record | partial | 16.9 / 25 | 117 public repos, account ~1 yr old |

### Package maintenance — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Published & resolvable | met | 25 / 25 | 1 package(s) on go |
| Publish recency | met | 35 / 35 | latest publish 12 days ago |
| Version history | met | 20 / 20 | 28 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

## Engineering Quality — 70/100 (Good)

Are baseline engineering and documentation practices in place? Weight: 19% of the overall index.

### Engineering practices — 60/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 5 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | not met | 0 / 16 | — |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | excluded | 0 / 20 | OpenSSF Scorecard unavailable |

### Documentation — 85/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | met | 25 / 25 | — |
| Documentation / homepage site | not met | 0 / 15 | — |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 7 topics |
| Wiki | met | 10 / 10 | — |

## Security — 46/100 (Weak)

Are visible security and supply-chain practices strong, with no malicious dependency and no unresolved high-risk jurisdiction exposure? Weight: 16% of the overall index.

### Security posture — 33/100 (At Risk)

Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Security policy (SECURITY.md) | not met | 0 / 30 | — |
| Dependabot config | met | 25 / 25 | — |
| Dependency lockfiles | excluded | 0 / 25 | published library — lockfiles are an application concern, not expected |
| CodeQL workflow | not met | 0 / 20 | — |

### Dependency advisories — 100/100 (Exceptional)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 135 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Direct dependencies free of known advisories | met | 35 / 35 | no direct dependency carries a known advisory |
| Indirect dependencies free of known advisories | excluded | 0 / 25 | transitive set not separable from development and test dependencies in this scope |
| No advisories left outstanding | excluded | 0 / 40 | no advisory carries a publication date |

### Malicious dependencies — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| No dependency reported as a malicious package | met | 100 / 100 | no dependency is reported as a malicious package |

## AI Readiness — 48/100 (Weak)

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight: agent tooling is a real maintenance signal, but its absence must never gate the top of the scale (calibration saturates at raw 91, so 100/100 remains reachable with AI Readiness at zero).

### Agent context & guidance — 1/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | not met | 0 / 45 | no CLAUDE.md / AGENTS.md / editor rules |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | partial | 1.2 / 40 | 1 of 45 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 67/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | partial | 12.6 / 18 | go.mod (toolchain convention, no task runner) |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | not met | 0 / 11 | — |
| Static type checking | met | 11 / 11 | Go (statically typed) |
| Reproducible environment | met | 10 / 10 | Dockerfile, lockfile |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 46 |
| Automated maintenance | partial | 5 / 8 | dependency automation configured, none observed in the sampled commits |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Code legibility for models — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | Go (statically typed) |
| Manageable file sizes | met | 55 / 55 | 0/15 source files over 60KB |

### Machine-readable interfaces — 40/100 (Weak)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| API schema (OpenAPI/GraphQL/proto) | not met | 0 / 40 | — |
| MCP server | not met | 0 / 20 | — |
| Runnable examples | met | 40 / 40 | example |

## Collection warnings

- OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

## What this report is

inspect.software measures public repositories against a single published, versioned methodology and reports the result as a 1–100 health index. Findings are signals derived from what is visible in public repository data — they are not a security audit, a warranty, or an endorsement, and no result depends on payment.

- Methodology, formulas and weights: https://inspect.software/methodology.md
- What a result does and does not claim: https://inspect.software/wiki/signals-not-warranties.md
- Rating bands: https://inspect.software/wiki/scoring-bands.md
- Corrections: https://inspect.software/contact.md
- Index of all documents: https://inspect.software/llms.txt