Limits and coverage.

A finding is a warning sign. Read the linked evidence before you choose a response. Each detection path has its own limits.

Vulnerable software

Suspicious activity

Works today

Tested in set scenarios

  • Reads installed packages from dpkg and apk databases and from requirements.txt, poetry.lock, package-lock.json, go.sum and Cargo.lock.
  • Matches exact versions, plus SemVer ranges for Go, npm and Rust crates, against a local signed advisory snapshot.
  • Checks the recorded inventory again when a new snapshot arrives. The agent can fetch one every 6 hours from an endpoint you configure.
  • Producer tools compile OSV, GHSA, KEV and EPSS records into a snapshot when you run them by hand.
  • Records selected program, network, persistence and decoy findings in a local hash chain the agent verifies.
  • Shows findings as CLI JSON, on a local API, and in the systemd journal when it runs as a service.
  • Private trial: a notification service you configure emails host, issue, severity and a sign-in link to acknowledge, and emails when a heartbeat goes overdue.

Not built yet

Planned or out of scope today

  • RPM databases, and Composer, Gemfile, pnpm and yarn lockfiles.
  • Identifying PHP, Ruby or Node runtime versions.
  • Distro backport and vendor fix versions. Until then, upstream version comparison can raise false alerts.
  • Fixed versions and reference links in a finding.
  • Marking a finding verified when the next check finds the fixed version.
  • A maintained advisory feed, or a scheduled producer run.
  • Blocking a process, or patching for you.
  • A hosted service, and measured results on production servers.
  • Agent-first setup: the setup prompt, command schemas, resumable sign-in, agent adapters and the test alert.