@decocms/blocks-cli@7.69.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 agent configuration changes are concrete but occur only as part of an explicit migration command, so the source does not establish an install-time attack. Warn about the persistent project-level rule and cleanup of src/AGENTS.md.
Decision evidence
public snapshot- The manifest exposes migration as a CLI command and lists no npm install lifecycle hook.
- The migration runs scaffold and cleanup; scaffold writes a project-local Cursor rule, with dry-run checks guarding writes.
- The generated rule is marked alwaysApply and points to the upstream migration policy; cleanup includes src/AGENTS.md in its deletion set.
- This behavior requires a user to run the migration command; the inspected source does not establish install-time agent configuration changes or a control hijack.
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/sync-blocks-to-kv.tsView on unpkg · L80Findings
Affected versions and remediation
This report applies to @decocms/blocks-cli@7.69.1.
See all versions of @decocms/blocks-cli for other recorded verdicts.
- Review the evidence and your use of @decocms/blocks-cli@7.69.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.