@decocms/blocks-cli@7.79.6
Deco codegen (generate-blocks, generate-schema, generate-invoke) and Fresh-to-TanStack migration tooling
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe agent configuration is installed only through an explicit migration command, so the source does not establish unconsented lifecycle abuse. However, the generated always-applied Cursor rule contains destructive recovery guidance, leaving a concrete project-level risk that warrants a warning.
Decision evidence
public snapshot- package.json exposes CLI commands and has no install lifecycle script.
- Running the migration command proceeds through scaffold and cleanup phases.
- The scaffold writes an always-applied Cursor rule into the migrated project.
- That rule advises an agent to delete the working tree and rerun if migration fails.
- Cleanup also removes src/AGENTS.md during migration.
- The agent configuration changes occur as part of the explicitly invoked migration command, not during package installation.
- The Cursor rule is first-party migration guidance; the inspected source does not show it executing a 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.79.6.
See all versions of @decocms/blocks-cli for other recorded verdicts.
- Review the evidence and your use of @decocms/blocks-cli@7.79.6 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.