Jev in production › Code and security review
jev-spec
An npm CI tool asks Jev one typed question per Markdown spec requirement, failing the build when code and probability drift below threshold.
The source publishes no measured number.
- Use
- Code and security review
- Industry
- Developer tools
- Form
- Open-source tool
- Stage
- Beta
- Listed
- 2026-09-29
- Found via
- github
- Repository
- nozomi-koborinai/jev-spec
- Stars
- 11
- Forks
- 3
- Last push
- 2026-09-29
- Language
- TypeScript
- License
- MIT
The README opens with
Catch spec drift on every commit. jev-spec checks your code against the requirements in your Markdown specification and fails the build when they drift apart. It asks TypeSafe AI's Jev model one focused question per requirement, gets a probability back, and compares it with a threshold you set. That makes it small enough for a pre-commit hook and strict enough for a CI gate.
Example report. The layout is what the CLI prints (timing and cost lines omitted); the probabilities are illustrative.
Badge
For the project's own README, linking back here:
Also used for code and security review
- fingers (chainreactors) 1-2
- jgrep 92%
- JevGate $0.050
- Jevscan 56/60
- eslint-plugin-jev (ShahriarBijoy) ~100 ms
- jev-attack-surface-analysis about one cent per repo scanned
- JeVerifier 19-20 of 20
- prompt-fossils 460 of 617