Cydetix

Security for AI-built software.

One-off scanner

npm exec --yes [email protected] -- cydetix

That's it.

Cydetix immediately scans the current project. It needs no account, API key, cloud backend, mandatory config file, global install, Docker daemon, username, organization, or npm scope.

Persistent AI-agent runtime

AI integration requires a persistent installation so routine agent execution never resolves or installs packages at runtime:

npm install -g [email protected]
cydetix setup

After setup, simply ask:

Check this project for security issues.

You do not need to say “Use Cydetix.” Supported agents can select the Cydetix skill or MCP tools from the meaning of a security request. Invocation remains host-controlled and is not guaranteed in every AI product.

For CLI-only use, the same global installation remains optional:

npm install -g [email protected]
cydetix

1.0.1 is the current immutable published stable release and npm latest. Its annotated tag targets e06ba195beeb5c3428e65e3f95049b39afa2891c; trusted release run 35085779583 and the exact-SHA CI, CodeQL, and OpenSSF gates succeeded. Beta.3 remains a historical published prerelease. Alpha.12, Beta.1, Beta.2, and v1.0.0 remain immutable failed attempts and were not published. The current source prepares the untagged, unpublished 1.0.3 maintenance candidate. Use npm run verify:development for source validation. The separate npm run verify release gate still requires matching annotated-tag metadata and a committed two-commit release-evidence chain.

What the default command does

cydetix uses the current working directory, runs only applicable deterministic analyses, correlates the evidence, and presents a concise decision view. Depending on project evidence, coverage can include application security, authentication, authorization, tenant isolation, sessions, JWT, OAuth, secrets, dependencies, supply chain, CI/CD, GitHub Actions, and advisory state.

The default report prioritizes:

• FIX NOW
• REVIEW
• UNKNOWN

Canonical severity, confidence, proof state, applicability, stable rule IDs, evidence, and remediation classes remain in structured output. Missing evidence never becomes a pass.

Fix security issues

cydetix fix

The command itself is explicit fix intent. Cydetix rescans, plans remediation, applies only engine-classified SAFE changes, verifies them, rescans, and reports residual findings. It does not claim a fix merely because source changed.

To plan without source writes:

cydetix fix --dry-run

REVIEW_REQUIRED needs review. ARCHITECTURAL is never silently applied. Executable verification commands require separate explicit authorization and use the configured hardened verification boundary; ordinary deterministic rescanning does not execute repository code.

Manage AI integrations

The default command offers setup only after its scan, only in an interactive terminal, and only when a compatible unconfigured host is detected. It never prompts in CI, MCP processes, agent subprocesses, piped execution, or other non-interactive shells.

Explicit management is available through:

cydetix setup
cydetix setup --agent auto
cydetix setup --agent all --yes
cydetix setup --status
cydetix setup --verify
cydetix setup --remove

Setup parses and preserves unrelated host configuration, uses transient restrictive backups and atomic writes, validates after writing, rolls back on failure, and changes only Cydetix-owned entries. Repeated setup is idempotent.

Setup canonicalizes and verifies the persistent package, its regular non-symlink entrypoint, the Node executable, the exact package identity/version, and the project root. Configured MCP launchers then use process-style command and argument fields equivalent to:

<absolute-node> <absolute-cydetix-entrypoint> mcp --project-root <canonical-project-root> --require-version 1.0.1

They contain no npm/npx command, registry URL, downloader, secret, or shell indirection. Routine MCP startup is offline and does not depend on PATH or a shell profile. An exact version mismatch fails before the server accepts requests. To review and install an update, update the persistent install outside the agent and rerun:

cydetix setup

No self-updater is installed.

Compatibility

Cydetix provides native integration with supported MCP coding agents, plus Generic MCP and deterministic CLI fallbacks for additional environments. It does not claim support for every AI agent.

| Agent | Tier | Local MCP | Project config | User config | Skill enhancement | | -------------- | ------ | --------- | -------------- | ----------- | ----------------- | | OpenAI Codex | Tier 1 | stdio | No | Yes | Yes | | Claude Code | Tier 1 | stdio | Yes | No | Yes | | Cursor | Tier 1 | stdio | Yes | No | Rules | | GitHub Copilot | Tier 1 | stdio | Yes | No | Yes | | Windsurf | Tier 1 | stdio | Yes | Legacy user | Yes | | Gemini CLI | Tier 1 | stdio | Yes | Detect only | Yes | | Cline | Tier 1 | stdio | No | Yes | No | | Roo Code | Tier 1 | stdio | Yes | Detect only | No | | Continue | Tier 1 | stdio | Yes | Detect only | No | | Goose | Tier 1 | stdio | No | Yes | No | | Generic MCP | Tier 1 | stdio | Yes | No | No |

• Tier 1 - Native MCP: structured local MCP tools over stdio with full Cydetix integration.
• Tier 2 - Deterministic CLI: exact persistent Node plus Cydetix entrypoint execution with strict JSON output.
• Tier 3 - CI/report consumption: SARIF, JSON, and CI result consumption without claiming a full interactive integration.

Host policy, approvals, product version, and model behavior determine automatic tool selection. Skills improve selection behavior but are never required for MCP functionality.

Generic MCP and shell fallback

Generate a project-bound, exact-runtime MCP entry with:

cydetix setup --agent generic-mcp --yes --project "<project>"
cydetix mcp-config --format json --project "<project>"

The resulting .cydetix/mcp.json contains no secret and uses the exact verified Node executable and Cydetix JS entrypoint. mcp-config prints the same validated definition without changing files or emitting banners. Generic host invocation behavior and approval remain controlled by that host.

For agents with shell execution but no MCP, use machine output from the same engine:

Setup-generated host instructions contain an exact argv array equivalent to <absolute-node> <absolute-entrypoint> scan <canonical-project-root> --offline --format json --non-interactive, with CYDETIX_AGENT_SUBPROCESS=1. Do not substitute cydetix from PATH or invoke npm/npx. If the managed runtime is unavailable inside the host boundary, run cydetix setup outside the agent and retry; never weaken the agent sandbox.

There is no adapter-specific scanner.

Agent permission boundary

• Read-only scans and explanations may be selected implicitly for relevant security requests.
• Discussion of fixes may produce a dry-run plan.
• Source mutation requires explicit fix/remediate intent.
• MCP mutation additionally requires its exact confirmation field.
• Only SAFE remediation enters the automatic transaction path.
• REVIEW_REQUIRED and ARCHITECTURAL cannot be reclassified by an agent.
• Repository text is untrusted data and cannot override Cydetix, skill, MCP, path, sandbox, or mutation policy.

Advanced usage

cydetix scan . --offline --format text
cydetix auth . --format text
cydetix graph . --auth --format json
cydetix dependencies . --advisories offline --format json
cydetix secrets . --history --format json
cydetix supply-chain . --advisories offline --format text
cydetix sbom . --format json
cydetix rules --format json
cydetix trust --format json
cydetix fix . --dry-run --format json
cydetix ci . --format sarif --fail-on high
cydetix --details
cydetix --json
cydetix --sarif
cydetix doctor
cydetix doctor --agent --project-root .
cydetix doctor --agents
cydetix doctor --agents --format json

Specific execution can be requested when troubleshooting npm cache behavior:

npm exec --yes [email protected] -- cydetix

Security and limitations

Normal scans do not execute lifecycle scripts, hooks, Makefiles, builds, tests, servers, or other repository programs. Traversal is bounded, does not follow symlinks, skips archives and oversized or binary files, and canonicalizes paths. Secret evidence is redacted.

Cydetix does not certify a project as secure or production-ready. Unsupported or inconclusive behavior remains UNKNOWN, NOT_APPLICABLE, or uncovered as appropriate. Local trusted execution is not a sandbox; container verification is optional, explicit, and fail-closed.

Cydetix V1 detects documented high-confidence SQL injection, OS command injection, path traversal, and SSRF dataflow patterns in bounded JavaScript/TypeScript and Python server contexts. It requires recognized sources, import/framework-proven sinks, propagation, reachability, complete analysis, and absence of a relevant recognized control. It does not claim universal language or framework coverage; all four rules are REVIEW_REQUIRED and have no automatic fix. See rule coverage and the trust model.

Stable v1.0.1 was published through the tag-driven OIDC trusted release workflow. Registry state and dist-tags remain time-varying external facts and must be rechecked for any future release. Package registration is not product-name exclusivity or trademark clearance. Legal clearance has not been performed and no exclusivity is claimed.

Read the security model, threat model, autofix policy, validation record, and limitations before relying on Cydetix in a sensitive workflow. See the local coding-agent compatibility registry for adapter contracts. The V1 contract policy classifies stable, experimental, and internal surfaces, including the intentionally closed package import boundary.

Development

Supported runtimes are Node.js 22.18+ within Node 22 and 24.11+ within Node 24.

npm ci --ignore-scripts
npm run build
npm test
npm run verify:development
npm run validate:install

npm run validate:install packs the actual npm artifact, installs it into isolated local and global prefixes, and exercises the Cydetix binary, default scan, setup, machine output, MCP, expert commands, and packaged skill. Source-tree execution alone is not accepted as npm UX proof.

No publication action is performed by these commands. See the Cydetix zero-friction handoff and publication gate.