@decocms/blocks-cli@7.50.1
Deco codegen (generate-blocks, generate-schema, generate-invoke) and Fresh-to-TanStack migration tooling
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe destructive recommendation creates a concrete agent capability risk, but it is added by an explicitly invoked migration command rather than an install hook. This supports a warning, not a publish block.
Decision evidence
public snapshot- The manifest exposes `deco-migrate` as a CLI and has no npm install lifecycle hook; its npm scripts are build, test, typecheck, and lint commands.
- The migration invokes the scaffold phase, which writes `.cursor/rules/migration-tooling-policy.mdc`.
- The generated Cursor rule is always applied and advises agents to delete the working tree and rerun after a failed migration.
Source & flagged code
5 flagged · loading sourcePackage source references child process execution.
scripts/audit-observability-config.test.tsView on unpkg · L309A single source file combines environment access, network access, and code or shell execution; review context before blocking.
scripts/sync-blocks-to-kv.tsView on unpkg · L77Findings
Affected versions and remediation
This report applies to @decocms/blocks-cli@7.50.1.
See all versions of @decocms/blocks-cli for other recorded verdicts.
- Review the evidence and your use of @decocms/blocks-cli@7.50.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.