# m62624/pi-code-planner — health index 63/100 (Moderate)

> Inspection of the public repository m62624/pi-code-planner by inspect.software. It holds a health index of 63 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/m62624/pi-code-planner
- Report page: https://inspect.software/software/m62624/pi-code-planner
- Full JSON report: https://inspect.software/api/repositories/m62624/pi-code-planner/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/m/m62624/pi-code-planner.svg
- Inspected: 2026-07-22
- Methodology: metrics 1.13.0, report schema 0.26.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 77/100 | Good |
| Community & Adoption | 18% | 35/100 | At risk |
| Sustainability & Governance | 24% | 53/100 | Moderate |
| Engineering Quality | 20% | 86/100 | Excellent |
| Security | 16% | 61/100 | Moderate |
| AI Readiness | not counted | 82/100 | Good |

## Repository facts

| Field | Value |
|---|---|
| Description | Structured planning, bounded memory, TDD, and Git guardrails for local coding models in Pi Code (I don't know TypeScript at all; this is mostly a local-model experiment, with occasional help from Claude Code) |
| Homepage | https://www.npmjs.com/package/pi-code-planner |
| Primary language | TypeScript |
| License | MIT |
| Stars | 4 |
| Forks | 1 |
| Created | 2026-05-14 |
| Last push | 2026-07-22 |
| Latest release | v0.12.1 |
| Commits (last year) | 382 |
| Bus factor | 1 |
| Topics | locally-generated, pi-code-extension, ai-slop, pi-extensions, pi-package, local-llm, local-llm-agent, llm-tools, vibe-coded |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | pi-code-planner | 0.12.1 | 3,041 |

## Vitality — 77/100 (Good)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 0 days ago |
| Commit cadence | partial | 6.9 / 36 | 10/52 weeks with commits |
| Commit volume | met | 18 / 18 | 382 commits in the last year |
| OpenSSF Scorecard: Maintained | not met | 0 / 10 | project was created within the last 90 days. Please review its contents carefully |

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

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

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

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 7.7 / 60 | 4 stars |
| Forks | not met | 0 / 25 | 1 forks |
| Watchers | not met | 0 / 15 | 0 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 | — |

### Ecosystem adoption (downloads) — 58/100 (Moderate)

Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | partial | 46.4 / 80 | 3,041 downloads/month across npm |
| Registry dependents | excluded | 0 / 20 | not reported by this ecosystem |

## Sustainability & Governance — 53/100 (Moderate)

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) — 10/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 | 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 | 105/105 decided PRs merged |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/21 approved changesets -- score normalized to 0 |

### Ownership & stewardship — 49/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 | 8.2 / 25 | 13 followers of m62624 |
| Track record | partial | 21 / 25 | 16 public repos, account ~7 yr old |

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

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

## Engineering Quality — 86/100 (Excellent)

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

### Engineering practices — 84/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 5 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | biome.json |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | met | 20 / 20 | 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |

### Documentation — 90/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | met | 25 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://www.npmjs.com/package/pi-code-planner |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 9 topics |
| Wiki | not met | 0 / 10 | — |

## Security — 61/100 (Moderate)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | partial | 3 / 7.5 | branch protection is not maximal on development and all release branches |
| CI-Tests | met | 2.5 / 2.5 | 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |
| 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/21 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 | met | 10 / 10 | no dangerous workflow patterns detected |
| 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 | not met | 0 / 7.5 | project was created within the last 90 days. Please review its contents carefully |
| Packaging | met | 5 / 5 | packaging workflow detected |
| Pinned-Dependencies | partial | 1 / 5 | dependency not pinned by hash detected -- score normalized to 2 |
| SAST | met | 5 / 5 | SAST tool is run on all commits |
| Security-Policy | not met | 0 / 5 | security policy file not detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | not met | 0 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | partial | 6 / 7.5 | 2 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 228 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 |

### High-Risk Jurisdiction Exposure — 100/100 (Excellent)

Only high-confidence self-published location evidence affects this multiplier. Ambiguous matches are review-only; country evidence is not proof of nationality, citizenship, legal registration, malicious intent, or sanctions status.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Policy exposure multiplier | met | 100 / 100 | no confirmed policy-scope location match |

## AI Readiness — 82/100 (Good)

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 — 85/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | met | 45 / 45 | .github/AGENTS.md, AGENTS.md, instructions/AGENTS.md, instructions/defaults/AGENTS.md, src/AGENTS.md, src/git/AGENTS.md, src/guard/AGENTS.md, src/instructions/AGENTS.md, src/project-local/AGENTS.md, src/runtime/AGENTS.md, src/session/AGENTS.md, src/settings/AGENTS.md, src/storage/AGENTS.md, src/vrf/AGENTS.md, src/worktree/AGENTS.md |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | met | 40 / 40 | 71 of 71 human commits state their intent (structured subject or explanatory body) |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | biome.json |
| Static type checking | met | 11 / 11 | tsconfig.json |
| Reproducible environment | met | 10 / 10 | lockfile |
| Demonstrated agent practice | met | 10 / 10 | 66 of the last 100 commits agent-authored or agent-credited |
| Automated maintenance | met | 8 / 8 | 3 of the last 100 commits are automated dependency updates |
| OpenSSF Scorecard: Pinned-Dependencies | partial | 2 / 10 | dependency not pinned by hash detected -- score normalized to 2 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | TypeScript (statically typed) |
| Manageable file sizes | partial | 54.2 / 55 | 3/219 source files over 60KB |

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- deps.dev does not index npm:pi-code-planner@0.12.1; advisories assessed against the repository dependency graph instead

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