JS 1.0 · Representative cases

Inspect representative JS 1.0 cases

Move from aggregate behavior to concrete source patterns. These cases explain why unmatched reports require inspection and why stable model output can remain incomplete.

Case context

Small fixtures make divergent evidence inspectable

Tigerteam is a compact JavaScript application containing deliberate vulnerability-shaped patterns. Nightowl is the largest app-like JS 1.0 fixture, with routes, uploads, database state, attachment flows, and frontend JavaScript.

Snyk Code defines the release reference set. Model matches and misses below are interpreted against that set; unmatched reports are not automatically false positives.

Published case evidence

Similar report labels can require opposite conclusions

SQL-shaped reports in two fixtures recurred identically, but source inspection separates a non-executable decoy from a likely deterministic-reference gap.

False-positive-shaped report

Tigerteam: SQL-shaped code without an executable sink

25 of 25 model runs reported the SQL-shaped decoy.The helper logs a string and returns an empty array; it never sends the constructed query to a database.

function dbQuery(sql) {
  console.log("Query:", sql);
  return [];
}

This is the kind of vulnerability-shaped pattern an LLM can describe plausibly even when the required execution sink is absent.

Likely product-gap candidate

Nightowl: unmatched SQL injection with a real database sink

25 of 25 model runs reported the likely SQL injection gap.Unlike Tigerteam, this helper concatenates an identifier into an executable SQLite statement.

deleteTodo: (id) =>
  db.prepare("DELETE FROM todos WHERE id = " + id).all()

It remained unmatched because it was outside the Snyk Code reference set. That status should trigger investigation, not automatic dismissal.

Systematic coverage gap

Nightowl: stable output can still be incomplete

Claude Opus 4.6 High held a stable 40.0% Snyk-reference F1 while missing15 of 15 path-traversal opportunitiesand 10 of 15 resource-limit opportunities.

The model recognized representative high-signal issues but did not enumerate repeated vulnerable sinks as systematically as deterministic SAST.

All benchmark projects

Inspect project evidence

Open reference findings, normalized model evidence, recurrence, and licensed source context for each JS 1.0 fixture.

  1. JS Snippet (Plugin Installer): Find Vulnerabilities

    Small Express plugin installer service with shell-based package installation.

    3 reference findings
  2. JS Snippet (Report Preview): Find Vulnerabilities

    Small Express report preview service that builds saved dashboard metric objects.

    2 reference findings
  3. JS App (Knex/Postgres 3): Find Vulnerabilities

    Express.js app with Knex.js and PostgreSQL. Scaffolded from Cursor's Auto MAX mode.

    3 reference findings
  4. JS Todo App (SQLite 4): Find Vulnerabilities

    Todo app with SQLite and file attachments. Scaffolded from Cursor's Auto MAX mode.

    7 reference findings
  5. JS Todo App (SQLite 5): Find Vulnerabilities

    Uptime and health check app with Express. Scaffolded from Cursor's Auto MAX mode.

    11 reference findings
  6. JS Snippet (Import Profile): Find Vulnerabilities

    Small Express supplier import profile service with dynamic field mapping.

    1 reference findings
  7. JS App (Knex/Postgres 2): Find Vulnerabilities

    Express.js app with Knex.js and PostgreSQL. Scaffolded from Cursor's Auto MAX mode.

    3 reference findings
  8. JS Snippet (Redirect Handoff): Find Vulnerabilities

    Small Express workspace handoff service with redirect and cross-origin response handling.

    4 reference findings
  9. JS Snippet (Shelf Validator): Find Vulnerabilities

    Small Express shelf validation page with a client-side dashboard widget loader.

    3 reference findings
  10. JS App: Find Vulnerabilities 1

    Express.js app for benchmark testing

    7 reference findings

Evidence boundary

Cases support interpretation, not universal classification

These static Phase 1 cases summarize published evidence from dataset1.0.0. The implemented Findings explorer and project routes provide normalized signatures, recurrence, and licensed source context for deeper inspection.