CRYPT

The first vulnerability report you can play

CRYPT finds security holes that matter in your code's building blocks, opens one fix, and a person approves it.

Proof: a real fix PR, green CI, a human merge. See the chain

How to play (manual)

Works in your workflow: GitHub Action · Slack/Teams digest · CSV export (when #131 lands)

Plain text, no effects, game events announced.

The problem: 248 findings across 20 popular repos, 95.2% were noise, and 84.7% of dependencies had no owner.

CRYPT: finds the few vulnerable dependencies that matter, names an owner from CODEOWNERS, opens one fix PR, and a human merges.

Proof: lodash 4.17.15 to 4.18.1, CI green, merged by a human.

Watch it run (60 s) Play the creature For teams

  1. Exhume (scan)
  2. Graft (fix PR)
  3. Human merges
  4. Reraise (healed)
See your repo as a creature in about 15 seconds. No install. Public GitHub repo with a package-lock.json at the root (npm). Example:

The Bench holds the raid, trophies, ranks, Simulated CI, the gallery, sound and recording mode.

Import a scanner report

SARIF, Dependabot alerts, Trivy, Grype or Snyk JSON. Drop a file here or choose one.

Parsed in your browser. The file stays on your device and is not uploaded.

Try it on your own repo: npx @e-1305/crypt raid <path-or-github-url>

Built with Kiro: specs, steering and hooks

The Graveyard: every repo a creature

The raid

Time left: 15:00

Ready. Start the raid when the team is together.

Team risk removed: 0.00

Rank: Apprentice

Nights Without Possession: 0

Risk removed

Creature health 100 of 100. Heartbeat 50 beats per minute.

Creature health falls with every unhealed limb, weighted by risk.

Next rank: Surgeon in 3 heals.

Combo: none. Heal two limbs within 90 seconds to start a chain.

Possession spread: 0 percent. Heal the next limb.

Trophies 0 of 6

    Type RAID in the game input to start as well.

    Simulated CI

    Rehearsal (nothing leaves this page) See the real run

    Replays a dry-run graft for the first sick limb. No token, no network, nothing real changes.

    Plate I: the creature

    Loading the plate.

    Dependencies are every package in the lockfile. Findings are the ones with a known vulnerability. A limb spawns for a finding above the noise line, and you can GRAFT it. Findings below the line are low risk and stay as stitches.

    The crypt

    Playing: the demo creature.

    Proof: the real run

    On 2026-11-18 CRYPT opened a real fix PR on e-1305/crypt-demo. Each step links to the real GitHub page.

    1. Found: jquery 3.4.1 Possessed (in CISA KEV), lodash 4.17.15 Rotting. Live raid summaries: run 1, run 2.
    2. Fix PR opened by CRYPT: crypt-demo PR #1, lodash 4.17.15 to 4.18.1, one dependency.
    3. CI green: the test check on PR #1.
    4. Merged by a human: PR #1 merged by the repo owner, using GitHub's Merge button. The account whose token opened PR #1 also merged it; CRYPT has no merge call.
    5. Re-raised: lodash HEALED in the reraise run.
    6. Counter-proof: PR #2 [DEMO SABOTAGE] jquery, CI red, GRAFT_REJECTED, closed unmerged.

    What this shows: one demo repo, a lockfile-level finding (the package version is vulnerable), not proof that the vulnerable code is reachable.

    Read the full chain in docs/PROOF.md