-
Notifications
You must be signed in to change notification settings - Fork 0
Project Maturity
Yuki edited this page Jul 10, 2026
·
1 revision
The current architecture addresses the major maturity gaps from the earlier review:
| Area | Current status |
|---|---|
| Type safety | Source, tests, scripts, config, issue types, and public API are TypeScript based. |
| Testing | Unit tests cover config, CLI args, locale checks, hardcoded scanning, reports, package checks, and integration workflow. |
| Reports | Console, JSON, Markdown, SARIF, and HTML are supported. |
| Performance | A repeatable benchmark script exists for scanner and locale-check changes. |
| Errors | CLI errors include cleaner messages and optional debug stack traces. |
| API stability | Public types are exported from the package root. |
| Ecosystem | Prettier config, pre-commit template, ESLint plugin template, and VS Code extension template exist. |
- ESLint and VS Code integrations are templates, not full standalone products.
- SARIF output should be validated against any target code scanning platform before relying on platform-specific annotations.
- The classifier is deterministic and rule-based; it does not verify linguistic translation quality.
- Strict CI adoption should happen after allowlists and baselines are tuned.