# jordan-clayton/ribble — health index 34/100 (At risk)

> Inspection of the public repository jordan-clayton/ribble by inspect.software. It holds a health index of 34 out of 100, placing it in the At risk 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/jordan-clayton/ribble
- Report page: https://inspect.software/software/jordan-clayton/ribble
- Full JSON report: https://inspect.software/api/repositories/jordan-clayton/ribble/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/j/jordan-clayton/ribble.svg
- Inspected: 2026-07-21
- Methodology: metrics 1.13.0, report schema 0.17.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 46/100 | At risk |
| Community & Adoption | 18% | 24/100 | Critical |
| Sustainability & Governance | 24% | 38/100 | At risk |
| Engineering Quality | 20% | 17/100 | Critical |
| Security | 16% | 44/100 | At risk |
| AI Readiness | not counted | 32/100 | At risk |

## Repository facts

| Field | Value |
|---|---|
| Description | Real-time and offline audio transcription in Rust. |
| Primary language | Rust |
| License | MIT |
| Stars | 1 |
| Forks | 0 |
| Created | 2024-07-20 |
| Last push | 2026-06-03 |
| Latest release | v0.1.0 |
| Commits (last year) | 52 |
| Bus factor | 1 |

## Vitality — 46/100 (At risk)

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

### Development activity — 45/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | partial | 18 / 36 | last push 48 days ago |
| Commit cadence | partial | 6.9 / 36 | 10/52 weeks with commits |
| Commit volume | partial | 15.5 / 18 | 52 commits in the last year |
| OpenSSF Scorecard: Maintained | partial | 5 / 10 | 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5 |

### Release discipline — 47/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 1 releases published |
| Release recency | partial | 7.2 / 36 | latest release 671 days ago |
| Release cadence | partial | 12.6 / 27 | cadence unknown (single release) |
| OpenSSF Scorecard: Signed-Releases | not met | 0 / 10 | Project has not signed or included provenance with any releases. |

### Abandonment — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | maintenance record not established from the collected data |

## Community & Adoption — 24/100 (Critical)

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

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

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

### Community health — 50/100 (Moderate)

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

## Sustainability & Governance — 38/100 (At risk)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 24% 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 | partial | 0.5 / 22.5 | top contributor authored 98% of commits |
| Contributor breadth | partial | 2.7 / 13.5 | 2 contributors |
| OpenSSF Scorecard: Contributors | not met | 0 / 10 | project has 0 contributing companies or organizations -- score normalized to 0 |

### Issue & PR responsiveness — 72/100 (Good)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | excluded | 0 / 46.8 | no issues or no data |
| PR acceptance | met | 38.2 / 38.2 | 3/3 decided PRs merged |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/24 approved changesets -- score normalized to 0 |

### Ownership & stewardship — 36/100 (At risk)

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | partial | 10 / 30 | personal (user) account |
| Verified domain | excluded | 0 / 20 | not applicable to user accounts |
| Owner reach | partial | 4.3 / 25 | 3 followers of jordan-clayton |
| Track record | partial | 14.1 / 25 | 9 public repos, account ~3 yr old |

## Engineering Quality — 17/100 (Critical)

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

### Engineering practices — 1/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | not met | 0 / 24 | — |
| Tests present | not met | 0 / 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 | not met | 0 / 20 | 0 out of 3 merged PRs checked by a CI test -- score normalized to 0 |

### Documentation — 40/100 (At risk)

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

## Security — 44/100 (At risk)

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 — 30/100 (At risk)

Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Token-Permissions. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | not met | 0 / 7.5 | branch protection not enabled on development/release branches |
| CI-Tests | not met | 0 / 2.5 | 0 out of 3 merged PRs checked by a CI test -- score normalized to 0 |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | not met | 0 / 7.5 | Found 0/24 approved changesets -- score normalized to 0 |
| Contributors | not met | 0 / 2.5 | project has 0 contributing companies or organizations -- score normalized to 0 |
| Dangerous-Workflow | excluded | 0 / 10 | no workflows found |
| Dependency-Update-Tool | met | 7.5 / 7.5 | update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | partial | 3.8 / 7.5 | 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5 |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | excluded | 0 / 5 | no dependencies found |
| SAST | not met | 0 / 5 | SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | not met | 0 / 5 | security policy file not detected |
| Signed-Releases | not met | 0 / 7.5 | Project has not signed or included provenance with any releases. |
| Token-Permissions | excluded | 0 / 7.5 | No tokens found |
| Vulnerabilities | partial | 2.2 / 7.5 | 7 existing vulnerabilities detected |

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

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 672 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 (Excellent)

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

## AI Readiness — 32/100 (At risk)

How well is the repo equipped to be developed and maintained with AI coding agents? An independent, experimental badge — weight 0.0, so it is surfaced on its own and does not affect the overall health score.

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

Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

| 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 | excluded | 0 / 40 | no data |

### Verify loop (build / test / typecheck) — 29/100 (Critical)

Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | not met | 0 / 22 | — |
| Lint / format config | not met | 0 / 11 | — |
| Static type checking | met | 11 / 11 | Rust (statically typed) |
| Reproducible environment | met | 10 / 10 | lockfile |
| Demonstrated agent practice | excluded | 0 / 10 | no data |
| Automated maintenance | excluded | 0 / 8 | no data |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | no dependencies found |

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

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

## Collection warnings

- Could not fetch crates package 'ribble' from its registry

## 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