Purpose and audience

Define semantic expectations in perch.yaml, scoped to files or methods, and inspect the resulting code findings.

Evidence 1 ↗ · Evidence 2 ↗

How Jev fits

The System One client asks typed questions about supplied state, defaults to jev-latest and calls TypeSafe's API.

Evidence 1 ↗ · Evidence 2 ↗

Using the project

Run a scan, inspect ranked issues, then recheck an issue after a change; setup commands add instructions for supported coding assistants.

Evidence 1 ↗ · Evidence 2 ↗

Scope and limits

Scans and checks require PERCH_API_KEY. A follow-up perch check does not save its findings into the recorded results.

Evidence 1 ↗ · Evidence 2 ↗

Repository description

Semantic code linting with Jev

Project facts

Relationship to Jev
Jev application
Evidence
Code reference
Language
JavaScript
License
MIT
Origin
Original repository
Repository status
Not archived
Created
2026-09-16
Last code update
2026-09-24
GitHub stars
310
Evidence checked
Sep 30, 2026
Metadata checked
Sep 28, 2026
Check status
Up to date

Stars measure the whole repository, including work unrelated to Jev.

Evidence and scope

Code reference records the linked documentation or source. JevHunt has not independently run or benchmarked this project.

Evidence commit: eaa137bf229ba5947740ea0c82820bd5517b17fb

Discovered through: typesafe-field-guide.

How we review →

Suggest a correction · Claim this listing · Submit a project