AI Security Review
scanned 2d ago · by lpm-firewall-aiNo confirmed malicious attack surface. The package is a deployment CLI with explicit commands that scaffold repos, manage generated secrets, call configured providers, and run demo infrastructure.
Decision evidence
public snapshot- dist/init/init.js shells out to git/pnpm and writes project scaffolding when init is invoked.
- dist/demo.js runs Docker/SSH/Cloudflare demo automation and reads a Cloudflare token from config/env.
- dist/apply/apply.command.js can POST a reconcile summary to a user-configured Discord webhook.
- package.json has no npm lifecycle hooks; install/import does not run package code.
- bin dist/cli.js only dispatches explicit stricli commands.
- dist/resolve/resolve.js imports a user config path and calls Cloudflare only during resolve.
- File writes are package-aligned: intent, desired-state, app scaffolds, .secrets.json/status/access outputs.
- No AI-agent control-surface writes, persistence hooks, credential harvesting, or hardcoded exfiltration endpoint found.
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