Maturity baseline
Stage: operational
Score: 56/100
The core has a coherent product promise, explicit module boundaries, typed ESM exports, basic examples, a benchmark, and passing CI. It remains early operational software because mutation-critical filesystem and file-kind paths are lightly tested, coverage is low and unenforced, CI is Linux-only, the adapter writes non-atomically, repository security and branch gates are weak, release automation only verifies, and the shipped license/metadata are incomplete.
| Dimension |
Score |
product_clarity |
4/5 |
documentation_onboarding |
4/5 |
architecture_modularity |
4/5 |
testing_ci |
2/5 |
security_configuration |
2/5 |
operations_observability |
2/5 |
release_maintenance |
2/5 |
performance_reliability |
3/5 |
backlog_governance |
2/5 |
Evidence reviewed
- README.md and docs/PRODUCT.md state the exact-or-fail editing promise and success metrics; docs/ARCHITECTURE.md lists modules, flow, and invariants.
- src/index.ts provides one export surface, but src/hashline.ts is approximately 1,200 lines and FilesystemPiClient contains separate fallback edit behavior.
- The assessment run passed all seven tests; node experimental coverage reported 67.84% lines, 61.36% branches, and 75.36% functions, including 16.67% lines for file-kind.js and 33.05% for filesystem-client.js.
- .github/workflows/ci.yml runs Node 22 and 24 only on ubuntu-latest and does not declare least-privilege workflow permissions.
- src/filesystem-client.ts uses writeFile directly and does not call loadFileKindAndText before decoding or rewriting a path.
- Live main protection has no pull-request requirement and no required checks; native security scanning, Dependabot updates, and private vulnerability reporting are disabled.
- SECURITY.md and an operations/recovery guide are absent.
- LICENSE contains only the line MIT License; GitHub classifies it as Other, and package.json lacks repository, homepage, bugs, keywords, and engines metadata.
- .github/workflows/release.yml verifies a tag but neither packages an artifact nor creates a GitHub release; one GitHub release exists for v0.1.0.
- There are no open issues; the Roadmap milestone and roadmap label exist, while the initial foundation roadmap issues are closed.
Action issues created
Existing issue coverage
- No existing open issue was recorded as covering a maturity gap.
Review cadence
Reassess after the high-priority issues are completed or before the next significant release. Scores are directional engineering signals, not production telemetry or compliance certification.
Maturity baseline
Stage: operational
Score: 56/100
The core has a coherent product promise, explicit module boundaries, typed ESM exports, basic examples, a benchmark, and passing CI. It remains early operational software because mutation-critical filesystem and file-kind paths are lightly tested, coverage is low and unenforced, CI is Linux-only, the adapter writes non-atomically, repository security and branch gates are weak, release automation only verifies, and the shipped license/metadata are incomplete.
product_claritydocumentation_onboardingarchitecture_modularitytesting_cisecurity_configurationoperations_observabilityrelease_maintenanceperformance_reliabilitybacklog_governanceEvidence reviewed
Action issues created
Existing issue coverage
Review cadence
Reassess after the high-priority issues are completed or before the next significant release. Scores are directional engineering signals, not production telemetry or compliance certification.