Benchmarks

Basilisk uses an isolated, deterministic ground-truth lab to qualify the installed CLI and Electron desktop application. Both surfaces execute the same pinned probes and are scored against the same expected outcomes.

Latest Verified Results

PASS: the latest checked-in artifacts record 46/46 passing scenarios in both the CLI and desktop harnesses, with detection and scenario parity between the two surfaces.

Measured resultCLIElectron desktop
Scenario coverage46/46 passed46/46 passed
Vulnerable HTTP controls6 TP, 0 FP6 TP, 0 FP
Hardened HTTP controls6 TN, 0 FN6 TN, 0 FN
Precision / recall / accuracy1.00 / 1.00 / 1.001.00 / 1.00 / 1.00
Protocol controls20/20 passed20/20 passed
Runtime readinessNo scanner errorsBackend and renderer ready

The authorization matrix made 28 requests to each local HTTP target. The hardened target produced 0 authorization violations; the deliberately vulnerable target produced the 2 expected violations, and both outcomes were classified correctly.

Authorization targetRequestsViolations foundClassificationDuration
Hardened HTTP280Correct7.025 s
Vulnerable HTTP282Correct7.109 s

Recorded Performance

These timings come from a single repetition of the checked-in local run. They describe that run only and are not hardware-independent performance claims.

Surface and targetWall-clock timePeak RSS
CLI — vulnerable HTTP6.316 s4.17 MiB
CLI — hardened HTTP3.879 s3.90 MiB
Desktop — vulnerable HTTP10.887 sNot recorded
Desktop — hardened HTTP6.674 sNot recorded

The ground-truth manifest was current and CLI-to-desktop detection parity and scenario parity both passed. Its SHA-256 fingerprint is 2e1c088d51659a0d1d1fcc2a802c2bb34913224d3435a0ded8319aea9035b42c.

Inspect the machine-readable evidence in the repository:

Scenario Inventory

Each surface must cover exactly 46 duplicate-free scenarios:

Scenario groupCount
HTTP finding controls12
Authorization-persona controls14
WebSocket controls10
Hostile HTTP controls10
Total46

The target is local and synthetic. It does not fetch external URLs, execute shell commands, or query a real database.

What the Harness Measures

For CLI and desktop runs, the harness records:

  • true positives, false positives, true negatives, and false negatives;
  • precision, recall, specificity, F1, and accuracy;
  • authorization-control and protocol outcomes;
  • wall-clock timing and peak memory where supported;
  • report SHA-256 values and scanner errors;
  • a 95% timing confidence interval for repeated runs.

Release Gates

The deterministic lab requires precision and recall of 1.0, correct authorization classification, no scanner errors, all protocol controls passing, and identical scenario outcomes between CLI and desktop.

These figures apply only to the checked-in synthetic lab. They are regression gates, not a claim that Basilisk has perfect accuracy against hosted models. Live LLM behavior is nondeterministic and can change with model, provider, configuration, and time.

Reproduce the Run

Run the installed CLI benchmark:

python benchmarks/cli/run.py --repetitions 3

Run the Electron benchmark:

cd desktop
npm ci
npm run benchmark

Compare fresh CLI and desktop results without rerunning them:

python benchmarks/run_all.py --compare-only

Reports are written below benchmarks/results/. The parity result demonstrates that both supported interfaces produce the same outcomes for the controlled scenarios; it does not compare commercial LLM vendors or publish a universal jailbreak success rate.