AI Security Review
scanned 2d ago · by lpm-firewall-aiNo confirmed malicious attack surface. The package is a deployment CLI with user-invoked commands that scaffold repos, resolve/apply desired state, and manage demo infrastructure.
Decision evidence
public snapshot- dist/init/init.js runs git and pnpm during user-invoked init
- dist/demo.js runs docker/ssh/git-style demo setup and Cloudflare cleanup
- dist/resolve/resolve.js dynamically imports the user config path
- package.json has no install/preinstall/postinstall lifecycle hooks
- dist/cli.js only dispatches user-invoked Stricli commands
- Command execution is tied to documented init/demo/adopt/apply workflows
- Secrets are read from env/.env or generated into .secrets.json, then used for Cloudflare/Forgejo operations
- No foreign AI-agent files, shell startup files, VCS hooks, or autostart persistence writes found
- Network use is package-aligned deployment/control-plane API access
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