Hexdigest123/typesafe-commentArchived
User repository on GitHub
Small Python package that uses typesafe.ai to evaluate code comments on certain heuristics
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
A Python linter that scores code comments with System One on five heuristics — usefulness, readability, accuracy, redundancy, coverage — and fails the pipeline when a comment falls under a threshold.
Hexdigest123/typesafe-commentArchived
User repository on GitHub
Small Python package that uses typesafe.ai to evaluate code comments on certain heuristics
Repo stats from the GitHub API, cached Oct 2026.
Lint code comments with TypeSafe AI's System One model. Comments are scored on five heuristics (usefulness, readability, accuracy, redundancy, coverage); those below thresholds emit linter warnings and exit non-zero so pipelines block. Never embedded in source. Set it in the environment or load from a .env file (see .env.example): General environment always wins over .env values. Other env vars: TYPESAFEMODEL (default jev-latest), TYPESAFEAPIBASE, TYPESAFETIMEOUT, TYPESAFEMAXRETRIES.
Quoted from the project's README. Read the full README.
Watch out
Every comment costs a model call, so scan time and spend scale with comment count across the directory you point it at, and the default thresholds are tight enough that the README's own example lowers accuracy and coverage before use. Runs are model-driven, so they are not byte-reproducible, and an API error exits with the same code as a genuinely bad comment, which makes a failing pipeline ambiguous without reading the output. Module-level comments are skipped entirely, so coverage is narrower than the file list suggests. The five scores come from the model and the README documents thresholds for them but no validation of the scoring itself. Copy reviewed against the repository README on 2026-10-04, not from running it.
Original write-ups on what this entry is for.
Posts from builders shipping with Jev right now.