Tripwire

Sandboxed multi-scanner security for AI skills, MCP servers, and package trees — coverage honesty, SIE judging, heatmap posture, guided triage and fix. Scan what agents install; fail closed.

Meterian Security / Stability / Licensing badges mirror the public
Meterian project report
(dependency and policy scan for this GitHub repo — not a Tripwire scan adapter).
CI / Complexity badges reflect GitHub Actions on main. The Nightly badge is
A — comprehensive T4 (daily 02:00 UTC: Semgrep, CodeQL, full secrets/Trivy,
dashboard tests, coverage snapshots, complexity, dep audit). B — Supply chain
(SBOM / Meterian / Chalk) is weekly Mon 03:00 UTC; C — Mutation
(Stryker / mutmut, non-gating) is 1st+15th 04:00 UTC. PR CI is
ultra-minimal (ship-path coverage + OSV + targeted scans) — see
CONTRIBUTING and
docs/README.md § CI workflows.

Where do you want to go?

What Tripwire does

Tripwire helps technical teams assess AI skills, MCP servers, and package
manifests before they rely on them. It discovers targets, runs
the enabled scanner adapters in an isolated Modal sandbox, stores findings in
Supabase, and brings them together in one dashboard (Live or Mock) with coverage
honesty, optional SIE judging, and a guided triage/fix flow.

Optionally, after each scan batch it runs a tiered router: Superlinked SIE
triages findings, and Alibaba Cloud Model Studio escalates when scanners
disagree or coverage looks incomplete (ADR-0016).

Providers and scanners

Missing Snyk / Cisco / Tessl / Ossprey keys → that scanner reports skipped /
needs_setup / skipped_missing_credential rather than claiming a complete scan.
DepShield always runs when the sandbox image includes it (no secret sync).
When every package scanner is not_applicable or skipped (e.g. no Cargo Audit
and no other engine completed), the card is NO COVERAGE, not green.
UNSCANNED remains for never-run / no usable scan record.
Cargo / Rust crates: Cargo Audit (RustSec) runs when Cargo.lock or
Cargo.toml is present.
Capability honesty and evidence states: docs/STATUS.md ·
inventory: ARCHITECTURE §0 ·
Ossprey key allowlist: OPTIONAL_SCANNER_KEYS.

Who Tripwire is for

Tripwire is currently an early-adopter tool with a hands-on setup and management
component. It is a good fit if you are comfortable using a terminal and shell,
managing local tooling and environment variables, editing .env and other
configuration files carefully, creating cloud/vendor accounts, and using command
output to resolve a setup issue.

You do not need to be a security specialist, but you should be ready to interpret
findings and decide when to escalate them. The optional Mock preview is available
for evaluating the dashboard without accounts; real scans require the setup below.

If you plan to change Tripwire, start the contributor setup
after cloning: it installs the commit and push hooks before your first change.

Run your first Live scan

Follow this order before running a scan or opening the Live dashboard. The
Quickstart supplies the commands; the linked guides
explain each decision before you make it.

1. Check the required tools and install the CLI.
2. Create the accounts you need: Supabase,
   Modal, then add Snyk, Tessl, and Cisco
   (Skill/MCP LLM + optional AI Defense) credentials with the
   environment-variable procurement guide.
   DepShield needs no keys. Add OSSPREY_API_KEY when you have Ossprey access
   (otherwise that adapter skips safely). For optional post-scan routing
   (ADR-0016),
   also set up Superlinked SIE (required for routing)
   and optionally Alibaba Cloud Model Studio
   (escalation only). Key map for every .env name: env-vars.md
   (mirrors .env.example).
3. Create .env only after you have the values, then fill it with
   env-vars.md as the single key reference.
4. Bootstrap Supabase and deploy the Modal scan app with the
   Live setup commands.
5. Run a fixture scan and open the Live dashboard from the
   Quickstart. After routing, use
   tripwire route to
   re-run a batch and read router results
   for pathway strips and Escalated / SIE-only filters.

Supabase and Modal are required for Live results. If Snyk, Tessl, Cisco, or Ossprey
credentials are absent, Tripwire reports that scanner as skipped rather than calling
the scan complete.
SIE and Model Studio are optional: without SIE keys, scans still complete and auto-route
logs a warning and skips. With SIE but without Model Studio, SIE-only reviews still log.

Preview the dashboard (optional)

Use Mock demo data only when you want a no-account look at the UI; it does not replace
the Live setup above or produce a scan result. Prefer the
hosted demo when you
do not need a local clone, or watch the
demo walkthrough on YouTube.

git clone https://github.com/neomatrix369/tripwire.git
cd tripwire
node scripts/serve-dashboard.mjs

Open http://127.0.0.1:8765/.

On the dashboard toolbar, Skills can be triaged by Tessl quality score using
Quality ≥ 80, Quality < 80, and No quality score tabs (skills only;
MCP servers are excluded from quality buckets but remain visible on all tabs).

The first visit shows a landing intro screen (threat statistics, architecture overview,
shipped skills, and roadmap). Click Open Dashboard → to proceed to the scan results
view (primary Dashboard tab: inventory KPIs, filters, and cards). Use the secondary
Workflow tab for Run → Triage → Investigate → Fix → Verify → Report. Simple/Expert
on Workflow only changes finding-detail density, not which primary tab you are on.
Operator-visible judge/coverage narration and L→R soft-amend (parent target
meta, multi-select, role-labelled models) are IMPLEMENTED / VERIFIED (unit) on
main via Wave R slice 75 (PR #163);
Workflow chrome polish (shared panel typography + denser Triage filters) via
slice 76 (PR #165).
Dismiss the intro with Open Dashboard → before Workflow (the Workflow tab
does not clear the intro overlay). Slice 77 (branch) hardens Run CTA / count
reconciliation / triage disposition persistence / Verify honesty — see
docs/STATUS.md.
The "About" nav button toggles the intro back on at any time; the choice is
remembered in sessionStorage.

Visual identity v2: cream paper, tan primary CTA, and AA-readable ink tokens
(Fraunces display headings) — shipped via PR #96.
Screenshots in docs/screenshots/ regenerated 2026-09-21.

After installing the CLI, you can also validate target discovery locally without
accounts or a scan:

tripwire scan --dry-discover ./fixtures/skills/safe-csv-cleaner

What happens next

Tripwire’s Live path is a short pipeline. Each hop uses a concrete piece of the
stack (same names as the badges above):

Mock skips Discover→Scan→Store and still shows Review (plus router fixtures).
Without SIE keys, Route warns and skips; scanner results still store. Sample CLIs
for router backends (no full batch): prototypes/sie-studio/,
prototypes/model-studio/.

flowchart LR
  discover["Discover<br/>skills / MCP / package"] --> scan["Scan<br/>Modal + Cisco/Snyk/Tessl/DepShield/Cargo Audit/Ossprey"]
  scan --> store["Store<br/>Supabase"]
  store --> inventory["CLI inventory / coverage / evidence"]
  inventory --> route["Route optional<br/>SIE → Model Studio"]
  route --> review["Review<br/>Dashboard"]

How to read strips and filters after Route:
reading-router-results.md.

Screenshots

CLI scan — Modal (live)

Dashboard — Mock overview

Workflow — Run (Mock)

Skill — Red (Mock)

MCP — Red (Mock)

Full gallery (Escalated / SIE-only, Workflow Triage/Verify, severity filters, list view) → docs/screenshots/

Find the right guide

Full map (including planning / CI): docs/README.md.