Examples

Generated fixtures, not stale hand-authored payloads

The example library is generated from real engine fixtures in savvy-cli, so it stays honest about what the engine actually produces instead of drifting from hand-maintained sample JSON.

2 min readSource: seceng-scan-content/fixtures

Jump to analysis Go to next step

Three workflow shapes

Every generated example belongs to one of these categories.

Reading

Scanner workflow — target, invocation, findings JSON, SARIF, evidence manifest
Offensive-platform workflow — representative attack object, path qualification, chokepoint
Failure workflow — malformed input, timeout, partial output, safe error

Golden workflows, not hand-copied payloads

Every example on the generated examples reference is sourced directly from real fixtures in seceng-scan-content/fixtures/ — sample findings, scan results, evidence manifests, repo profiles, and disclosure records. None of it is placeholder text written for this site.

Draft — generated reference pending

These are sample/fixture data for docs and tests — not live customer output. Each is labeled as such in the generated reference.

What a good example needs

Engine and schema version it was produced against
The command or endpoint that produced it
Expected exit or job state
Known limitations — what it deliberately does not cover

Not every fixture in savvy-cli currently carries all of these annotations — the generated examples reference shows what metadata each fixture actually has today rather than backfilling assumed values.

Browse examples

Generated examples reference

Real fixture filenames and descriptions from the current savvy-cli sync.

View Generated Reference Open SecEng Developer Center