For security and cyber teams

The operator path: start read-only, gate CI on exit codes, scan the live app, then remediate through a pull request. The security model is the trust story.

Identity

What Erydas is

Erydas is open-source, deterministic dependency security and cyber defense for npm, live web apps, and AI-assisted teams. We read exact versions from package-lock.json, match them to disclosed OSV advisories (CVEs, GHSAs, and MAL malware records), scan live URLs passively, and apply the smallest verified direct-dependency update — or we change nothing. Advisory truth is . Optional AI can explain a confirmed finding. It never invents a vulnerability and never picks a version. The same scanner, live-edge recon engine, and fix planner run in the CLI, Cloud dashboard, API, SDK, MCP, and CI.

  • 01

    OSV is truth

    Disclosed advisories from OSV decide what is vulnerable — including CVE, GHSA, and MAL malware IDs. Erydas never scrapes forums, guesses CVEs, or lets a model invent findings.

  • 02

    The lockfile is inventory

    Exact installed versions in package-lock.json decide what is in the tree. A stale lockfile is an error, not a guess.

  • 03

    Mutation is gated

    Fixes are planned, approved, applied with lifecycle scripts disabled (--ignore-scripts), rescanned, and rolled back together if verification fails.

Surfaces

What we offer

One deterministic pipeline, every surface your stack touches. Solo engineers, security teams, CI, and coding agents share the same contracts.

  • CLI

    Open-source npm package

    eridas scan, fix, init, and tinfoil. Zero account required. Same deterministic planner Cloud uses under the hood — any laptop, CI runner, or agent sandbox.

    Commands
  • Cloud

    GitHub App and command center

    Connect an org once. Security posture overview, Guided and Dev UIs, queued scans, findings, and fix PRs on a dedicated branch. Never merges to default.

    Open Cloud
  • Live app

    Leveled passive site recon

    GET-only scan of any public URL: L1 surface, L2 exposure, L3 supply chain, L4 reconstruction. One report, a grade per level, in under a minute.

    Levels guide
  • API & SDK

    Headless /api/v1 & /api/v2

    Typed TypeScript client (@eridas/cloud-sdk) for scans, findings, remediations, investigations, repo sync, and long-poll wait. Stable JSON for SOAR and tickets.

    Docs
  • Agents

    MCP, SKILL.md, and llms.txt

    Native @eridas/mcp server for Cursor and editors, portable SKILL.md for Claude Code and Codex, and machine docs. Same flags, exit codes, and dry-run path as CI.

    For agents
  • CI

    Scheduled GitHub Actions

    eridas init writes a pinned workflow. Scan mode requests contents:read only. Fix mode opens or updates one reviewable PR on eridas/automated-remediation.

    Team runbook

Operators

How security and cyber teams run it

Start read-only. Gate CI on exit codes. Scan the live app. Connect GitHub when you are ready for pull-request remediation — never a push to default.

  1. 01

    Baseline the lockfile (read-only)

    Inventory exact installed versions against OSV. Use JSON in pipelines. Exit 1 means disclosed findings remain at your threshold — do not treat the tree as clean.

    $npx eridas scan . --quiet --format json
  2. 02

    Schedule a read-only watch

    Generate eridas.config.json and a GitHub Actions workflow with contents:read only. Keep this mode until you trust PR-based remediation.

    $npx eridas init . --mode scan
  3. 03

    Scan the live product

    Level 2 (default) covers exposure: headers, leaked .env/.git/source maps, secrets in bundles, public API docs. Level 3 adds the OSV supply-chain check. Scans are passive and refuse private addresses.

    $npx eridas tinfoil https://example.com --level 2
  4. 04

    Connect GitHub for the org

    Sign in to Erydas Cloud, install the GitHub App, create an erd_ API key. Store keys in CI secrets or local env — never in eridas.config.json. GitHub-gated endpoints return 403 until the App is installed.

    $eridas auth login
  5. 05

    Remediate on a pull request

    Promote to init --mode fix or open a Cloud remediation. Fixes land on eridas/automated-remediation for normal branch protection. --force skips the prompt only — not rescan, verification, rollback, or major policy.

    $npx eridas init . --mode fix
  6. 06

    Pin policy and prove the fix

    Keep allowMajor false until you opt in. Set verificationCommands (npm test, lint, typecheck). Pin the Erydas version in the generated workflow. Gate CI on exit codes 0/1/2/3.

    $npx eridas fix . --dry-run --quiet --format json

Operator checklist

  • Prefer eridas fix --dry-run before the first apply
  • Keep verificationCommands meaningful (npm test, lint, typecheck)
  • Use init --mode scan until you trust PR-based remediation
  • Pin Erydas via the generated workflow version string
  • Never commit API keys; use GitHub Actions secrets or local env only
  • Do not auto-merge to the default branch; review the remediation PR

Exit codes

0
Clean scan or successful operationContinue
1
Disclosed findings remain at the configured thresholdTriage findings; do not claim the tree is clean
2
Config, lockfile, network, or execution errorFix the operational issue and retry
3
Interactive fix approval declinedDo not retry apply without explicit intent

CI contract

Progress goes to stderr. JSON stays on stdout. Gate the job on the process exit code — not on log text.

npx eridas scan . --quiet --format json
npx eridas fix . --dry-run --quiet --format json
npx eridas tinfoil https://example.com --level 2 --format json

Scheduled automation: eridas init . --mode scan until the team is ready for PRs, then --mode fix. Fix mode updates one branch and one pull request; it never pushes to default.

Cloud for the org

Sign in, install the GitHub App, create an erd_ key. Drive the same pipeline from the dashboard, CLI, SDK, or MCP.

eridas auth login
eridas cloud repos
eridas cloud scan --repo-id <uuid> --wait --format json
eridas cloud findings --repo-id <uuid> --format json
eridas cloud remediate --repo-id <uuid> --wait --format json

GitHub-gated endpoints return 403 github_not_connected until the App is installed. Remediations open a PR; Cloud does not merge it.

Sources of truth

ConcernAuthority
What is installedExact versions in package-lock.json
What is disclosedOSV machine-readable advisories
What to installDeterministic planner from fixed versions
Whether to mutateHuman approval, --yes, or --force
Whether the fix workedOSV rescan + verification commands

AI is not a source of truth. Advisory text is untrusted before optional model prompts. Details: security model.

Deliberately out of scope for v0.1

  • Forum scraping or untrusted “leak” sites
  • Auto-merge to the default branch
  • Injecting npm overrides for transitive packages
  • Letting AI choose fixed versions
  • Storing credentials in eridas.config.json
  • Silent pnpm / Yarn support — those lockfiles are refused, not guessed

Vulnerability truth remains . Report suspected Eridas issues via SECURITY.md in the repository.

API & SDKCommandsSecurity model