AI Security Review
scanned 2d ago · by lpm-firewall-aiNo confirmed malicious install-time or import-time attack surface. Risky primitives are tied to explicit deployment/demo CLI commands and package-aligned infrastructure automation.
Decision evidence
public snapshot- dist/init/init.js user-invoked init runs git/pnpm and writes scaffold files
- dist/demo.js user-invoked demo manages Docker, SSH, Cloudflare demo DNS/tunnel
- package.json has no npm lifecycle hooks; bin only maps intentic to dist/cli.js
- dist/app.js registers explicit CLI commands; no import-time execution beyond CLI dispatch
- dist/resolve/resolve.js dynamically imports user config path for intended deploy resolution
- dist/apply/apply.command.js posts only to configured Discord webhook output and uses env secrets for deployment
- rg found no Claude/Codex/Cursor/MCP control-surface writes
Source & flagged code
4 flagged · loading sourcePackage source references child process execution.
dist/init/scaffold-app.jsView on unpkg · L1Package source references dynamic require/import behavior.
dist/resolve/resolve.jsView on unpkg · L6A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/demo.jsView on unpkg · L29Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/demo.jsView on unpkg · L29