AI Security Review
scanned 11h ago · by lpm-firewall-aiNo confirmed malicious attack surface. Network, package installation, file writes, and child-process execution occur only through explicit CLI commands for scaffolding, building, testing, auditing, or plugin/registry operations.
Decision evidence
public snapshot- package.json has only prepublishOnly; no install lifecycle hook.
- bin/street.js only delegates to runCli after user invokes street.
- dist/index.js dispatches named CLI commands; import reads local package.json and loads project .env.
- dist/commands/create.js writes a requested scaffold and runs npm only for create, lockfile generation, or --install.
- dist/commands/plugin.js and dist/commands/registry.js network actions require explicit plugin/registry commands.
- No eval/vm/native loader or AI-agent configuration path was found.
Source & flagged code
6 flagged · loading sourcePackage source references child process execution.
dist/commands/start.jsView on unpkg · L2Package source invokes a package manager install command at runtime.
dist/commands/test.jsView on unpkg · L73Source appears to send environment or credential material to an external endpoint.
dist/commands/create.jsView on unpkg · L398A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/commands/create.jsView on unpkg · L398Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/commands/generate.jsView on unpkg · L94