Skip to main content
Deployment review

DeploySutra AI

Kubernetes and plan review. It does not deploy.

Offline, read-only review of Kubernetes manifests and OpenTofu or Terraform plans. npm [email protected] published 2026-11-17. The command alias is deploysutra. The README says it never deploys, never touches a cluster, and needs no API key. The gate can only say BLOCKED or HUMAN_REVIEW_REQUIRED. There is no READY. On 2026-11-17 the npm downloads API returned no row, so both counts are 0. GitHub showed 0 stars and 0 open issues. The name DeploySutra has not been trademark-searched.

  • Offline
  • 19 rules
  • Node 20+
GitHub version
0.2.0
Licence
Apache-2.0
Language
JavaScript
Weekly downloads
0
Overall downloads
0
GitHub stars
0

Live npm weekly downloads, npm overall downloads, and the latest npm version, plus GitHub stars and the package.json version, fetched 2026-11-17 19:07 UTC. Cached 10 minutes. Weekly downloads cover 2026-11-10 to 2026-11-16. Overall downloads cover 2026-10-01 to 2026-11-17. npm does not publish an earlier total. Stars and downloads show public use. They are not a quality score.

Use it when

  • 1

    You have two versions of a Kubernetes manifest and want a sourced diff before a person decides.

  • 2

    You have an OpenTofu or Terraform plan JSON and want action counts without keeping state or addresses.

  • 3

    You want a gate that can only say BLOCKED or HUMAN_REVIEW_REQUIRED.

What it does, and what it does not

Read this before the guide. A limit here is a limit of the tool.

Does

  • analyze diffs two manifest versions. Containers match by name. The README says line numbers come from the parser and sensitive values are redacted.
  • 19 rules, DS-K8S-001 through DS-K8S-019. Profiles are development, staging, and production. New and persistent risk are both reported. explain prints one rule.
  • BlastMap links Service, workload, Ingress, ConfigMap, Secret, PVC, ServiceAccount, and role bindings that are in the files you gave it. Anything else is UNKNOWN.
  • The rollback ledger has five prerequisites. The README says a declaration is DECLARED_NOT_VERIFIED and is never called ready.
  • tofu summarizes an OpenTofu or Terraform plan: action counts, replacement, and data-bearing destructive actions. The README says no state, values, or addresses are kept. Truncation is flagged.
  • Reports are HTML, Markdown, and JSON. The README says the HTML has no JavaScript. verify checks the SHA-256 seal. Exit 3 means the report failed verification.
  • audit writes a self-audit bundle. MCP tools are read-only and scoped to one folder. The README says that check used a scripted JSON-RPC client, not MCP Inspector. 0 runtime dependencies. Node.js 20 or newer.

Does not

  • It does not deploy, apply, destroy, or roll back. The README says the audit checks that no such command exists.
  • It is not an admission controller. The README points to OPA or Kyverno for that. It is not an image scanner and not a compliance certificate.
  • A desired-state diff is not live drift. The README says the report is not proof of live state, network reachability, IAM scope, or recoverability.
  • Kubernetes input is YAML or JSON up to 1 MiB and 200 documents. Anchors, aliases, tags, merge keys, block scalars, Helm or Go templates, and symlinks are rejected. Render Helm or Kustomize to plain YAML first.
  • The README reports 312 tests (308 passed, 0 failed, 4 skipped symlink tests on a machine that cannot create symlinks; CI runs them) and a self-audit of 42 passed, 0 failed, 7 not run, recorded on Windows 11 with Node 24. A 50-case corpus is author-labelled and the README says it is not independent. This page did not re-run those checks.
  • The name DeploySutra has not been trademark-searched. A sealed report is not a certification.

Claims above are from the project pages and are attributed as stated there. They are not independently verified here.

How a run moves

From the DeploySutra AI README, npm 0.2.0, published 2026-11-17. It reads manifests or a plan file. It does not deploy.

  1. 1. Diff

    Desired state

    Two YAML or JSON versions. Line numbers and redacted values. This is not a live cluster diff.

  2. 2. Rules

    19 checks

    Public exposure, privileged containers, secrets in env, scale to zero, wildcard RBAC, and the rest of DS-K8S-001 through 019. A profile decides what blocks.

  3. 3. Rollback

    Five gaps

    A ticked box is DECLARED_NOT_VERIFIED. The README says a corpus with every box ticked still had no READY result.

  4. 4. Gate

    Two words

    BLOCKED or HUMAN_REVIEW_REQUIRED. Exit 2 is BLOCKED. Exit 0 is not an authorization to deploy.

How to read the result

Result It means It does not mean
BLOCKED The README says a new high finding or missing rollback evidence stopped the gate. Not a fix and not a deploy.
HUMAN_REVIEW_REQUIRED The static checks did not block. A person still decides. Not READY. The README says that word is not a possible gate.
UNKNOWN BlastMap had no edge for that link in the files you gave it. Not proof the link is absent in the cluster.

Wording is from the project page or README and is attributed as stated there. It is not independently verified here.

Commands and notes

  • npx [email protected] analyze --before old.yaml --after new.yaml --profile production --out report diff and gate. Exit 2 is BLOCKED.
  • deploysutra policy --input app.yaml --fail-on HIGH policy check on one file.
  • deploysutra rules and deploysutra explain DS-K8S-012 the rule list and one rule.
  • deploysutra tofu --input plan.json --out dir plan summary. No state kept.
  • deploysutra verify, audit, install-skills, and mcp listed in the README command table. mcp is read-only.

Guide

How to use the result. GitHub is the source repository. npm is the install.

What 0.2 reviews

From the DeploySutra AI README, npm 0.2.0, published 2026-11-17. Node.js 20 or newer. 0 runtime dependencies. The command alias is deploysutra.

  • npx [email protected] analyze --before old.yaml --after new.yaml --profile production --out report diffs desired state and writes HTML, Markdown, and JSON.
  • 19 rules, DS-K8S-001 through DS-K8S-019. Profiles are development, staging, and production. BlastMap only links objects in the files you gave it. Anything else is UNKNOWN.
  • tofu summarizes a plan file and keeps no state, values, or addresses. The rollback ledger marks declarations DECLARED_NOT_VERIFIED.
  • Exit 0 is ok. Exit 1 is an error. Exit 2 is BLOCKED. Exit 3 means the report failed SHA-256 verification.

What a review is not

  • The README says the tool never deploys and never touches a cluster. It is not OPA, Kyverno, an image scanner, or a compliance certificate.
  • A desired-state diff is not live drift and not proof of network reachability, IAM scope, or recoverability. The gate cannot say READY.
  • The README reports 312 tests (308 passed, 0 failed, 4 skipped) and a 50-case author-labelled corpus. It says nobody independent has reviewed the code. This site did not re-run the proof.
  • MCP was checked with a scripted JSON-RPC client, not MCP Inspector. The name DeploySutra has not been trademark-searched. On 2026-11-17 npm had no download row, so the snapshot count is 0.

Questions

Does DeploySutra deploy to my cluster?

No. The README says there is no apply, deploy, destroy, or rollback command, no cluster connection, and no API key. It reviews files you pass in. It does not replace OPA, Gatekeeper, or Kyverno.

Can the report say the release is ready?

No. The README says the only gate words are BLOCKED and HUMAN_REVIEW_REQUIRED, including when every rollback box is ticked. A desired-state diff is not live drift. The 50-case corpus is author-labelled, and this page did not re-run the 312 tests.

WhatsApp