Question 1

Is this another coverage wrapper that needs config or a reporter?

Accepted Answer

No. You append the command you already use after -- and Supercov runs it in an isolated workspace without changing your source, tests, runner configuration, or normal build output. Coverage needs no account, config file, import, custom reporter, or hosted service; everything local and free.

Question 2

Will the Jev scores actually mean anything, or are they vibes?

Accepted Answer

They are checkable claims. Scoring asks Jev a fixed set of yes/no questions about each file and does the arithmetic itself, so every part of a score maps to something you can read in the file. The output prints the checks that fired with their probabilities, and you can narrow to gaps, one file, or just a patch.

Question 3

What does it cost me, and is the key really needed?

Accepted Answer

The key is needed only for quality, security, and assertion assessment; coverage runs without one. Jev bills for what it reads and nothing for what it writes, which the README puts at a little over a cent per megabyte of source, and answers are cached by content so a second run pays only for what changed.

Question 4

Does it replace my coding agent?

Accepted Answer

No, and the README says so directly: Supercov supplies coverage signal and evidence and does not host, schedule, or replace your coding agent. The intended loop is that the agent picks one gap, writes a focused test, reruns the complete suite through Supercov, and then proves what improved with diff.

Question 5

How do I run it, and does it change my build?

Accepted Answer

Everything after -- is your test command, and Supercov runs it in an isolated workspace without changing your source, tests, runner configuration or normal build output: npx supercov -- npm test. You can also install via brew install supercorp-ai/tap/supercov or, for Go, go run github.com/supercorp-ai/supercov/cmd/supercov@latest.

Question 6

Which languages are supported, and where does the report go?

Accepted Answer

JavaScript, TypeScript, Rust, Python, Ruby, Go, Java and Kotlin are supported. The interactive report is written to .supercov/reports/, where the store's own .gitignore keeps it out of git, and it has no server, external assets, account or file picker, so you can attach that one file to a pull request.

Question 7

What does the security scan actually check?

Accepted Answer

Twelve security checks are asked of every file with the same key, from injection and secrets in source to paths and redirects taken from a request. Nothing is averaged: a file is clean, or it names what fired, with the line and the code on it where Jev confirms one.

Supercov

About this project

Highlights

Quickstart

Questions about this entry

Reactions & coverage

From the Jev guides

From the Jev AI model community