@decocms/blocks-cli@7.77.2
Deco codegen (generate-blocks, generate-schema, generate-invoke) and Fresh-to-TanStack migration tooling
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe scanner’s execution and network signals are consistent with CLI migration, generation, and test behavior; no install-time attack was identified. The generated Cursor instruction creates a conditional destructive capability, so a warning is appropriate.
Decision evidence
public snapshot- The manifest exposes `deco-migrate` as a CLI and lists no install lifecycle hook.
- The migration runs scaffold and cleanup phases; its bootstrap and provisioning phase is skipped in dry-run mode.
- Scaffolding writes a project-level `.cursor/rules/migration-tooling-policy.mdc` file.
- The generated Cursor rule is always applied and tells agents to delete the working tree after a failed migration.
- Cleanup removes `AGENTS.md` only from the source directory’s `src/` folder when cleanup runs.
- The agent configuration change requires an explicit migration command; no install-time agent configuration mutation was found.
- The destructive instruction is generated text for an agent to follow; the inspected source does not execute that deletion itself.
Source & flagged code
5 flagged · loading sourcePackage source references child process execution.
scripts/generate-workspaces.test.tsView on unpkg · L1A single source file combines environment access, network access, and code or shell execution; review context before blocking.
scripts/migrate.ts#virtual:normalized:round1View on unpkg · L94Findings
Affected versions and remediation
This report applies to @decocms/blocks-cli@7.77.2.
See all versions of @decocms/blocks-cli for other recorded verdicts.
- Review the evidence and your use of @decocms/blocks-cli@7.77.2 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.