# l0k18/9 — health index 13/100 (Critical)

> Inspection of the public repository l0k18/9 by inspect.software. It holds a health index of 13 out of 100, placing it in the Critical 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/l0k18/9
- Report page: https://inspect.software/software/l0k18/9
- Full JSON report: https://inspect.software/api/repositories/l0k18/9/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/l/l0k18/9.svg
- Inspected: 2026-08-28
- Methodology: metrics 2.10.0, report schema 0.34.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 20/100 | At Risk |
| Community & Adoption | 17% | 21/100 | At Risk |
| Sustainability & Governance | 23% | 30/100 | At Risk |
| Engineering Quality | 19% | 44/100 | Weak |
| Security | 16% | 17/100 | Critical |
| AI Readiness | 4% | 52/100 | Moderate |

The weighted overall 28 is calibrated to 22 on the published index scale (record calibration 2026-08-02). Abandonment Policy applies a 60% multiplier to weighted overall health and gives it a ceiling of 34.

## Repository facts

| Field | Value |
|---|---|
| Classification | application |
| Primary language | Go |
| Stars | 0 |
| Forks | 0 |
| Created | 2019-05-30 |
| Last push | 2019-05-30 |
| Latest release | v0.9.1 |
| Commits (last year) | 0 |

## Vitality — 20/100 (At Risk)

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

### Development activity — 1/100 (Critical)

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

### Release discipline — 48/100 (Weak)

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | partial | 16.2 / 27 | 2 version tags (no GitHub releases) |
| Release recency | not met | 0 / 36 | latest release 2677 days ago |
| Release cadence | met | 27 / 27 | a release every ~0.7 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### Abandonment — 60/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | partial | 60 / 100 | no human commit for 2647 days; 3 unmet obligation(s): a fixed advisory left unapplied, releases stalled, Scorecard reports it unmaintained |

## Community & Adoption — 21/100 (At Risk)

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

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

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

### Community health — 44/100 (Weak)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | partial | 16.9 / 22.5 | license file present, not a recognized license |
| 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 — 30/100 (At Risk)

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

### Issue & PR responsiveness — 1/100 (Critical)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | excluded | 0 / 42 | no issues or no data |
| PR acceptance | excluded | 0 / 30 | no decided pull requests or no data |
| Newcomer PR acceptance | excluded | 0 / 13 | no first-time contributor's PR decided in 30d |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/30 approved changesets -- score normalized to 0 |

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

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 | 11.7 / 25 | 42 followers of l0k18 |
| Track record | met | 25 / 25 | 91 public repos, account ~10 yr old |

## Engineering Quality — 44/100 (Weak)

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

### Engineering practices — 30/100 (At Risk)

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | not met | 0 / 24 | — |
| 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 | no pull request found |

### Documentation — 65/100 (Good)

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

## Security — 17/100 (Critical)

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 — 13/100 (Critical)

Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Signed-Releases, 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 | excluded | 0 / 2.5 | no pull request found |
| 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/30 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 | not met | 0 / 7.5 | no update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | partial | 2.2 / 2.5 | license file detected |
| Maintained | not met | 0 / 7.5 | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | not met | 0 / 5 | dependency not pinned by hash detected -- score normalized to 0 |
| SAST | not met | 0 / 5 | no SAST tool detected |
| Security-Policy | not met | 0 / 5 | security policy file not detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | excluded | 0 / 7.5 | No tokens found |
| Vulnerabilities | not met | 0 / 7.5 | 59 existing vulnerabilities detected |

### Dependency advisories — 35/100 (Weak)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 34 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 | partial | 4.4 / 35 | 4 affected: golang.org/x/crypto 0.0.0-20190513172903-22d7a77e9e5f (critical 10.0), google.golang.org/grpc 1.21.0 (critical 9.1), golang.org/x/net 0.0.0-20190522155817-f3200d17e092 (high 7.5), +1 more |
| 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 | partial | 21.6 / 40 | 4 advisory-carrying package(s) unaddressed past 90 days; oldest published 1961 days ago |

### 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 — 52/100 (Moderate)

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 | not met | 0 / 40 | 0 of 100 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 56/100 (Moderate)

| 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 | lockfile |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 100 |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | not met | 0 / 10 | dependency not pinned by hash detected -- score normalized to 0 |

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

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

### Machine-readable interfaces — 100/100 (Exceptional)

Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| API schema (OpenAPI/GraphQL/proto) | met | 40 / 40 | pkg/rpc/api.proto |
| MCP server | excluded | 0 / 20 | not applicable to this kind of software |
| Runnable examples | met | 40 / 40 | demos, examples |

## Collection warnings

- Contributor list unavailable
- Could not fetch go package 'git.parallelcoin.io/dev/9' 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