AI Security Review
scanned 7d ago · by lpm-firewall-aiNo confirmed malicious attack surface. The package is a Claude harness installer whose high-risk writes occur on explicit CLI use, while postinstall only prints instructions and exits.
Decision evidence
public snapshot- package.json defines postinstall: node scripts/install.js --post-install
- scripts/install.js can install Claude hooks/settings/skills into a project's .claude directory when run as CLI
- scripts/install.js uses npm view and git clone/pull against github.com/agilantsolutions/claude outside postinstall
- scripts/install.js --post-install exits after setup message before project .claude writes or git clone/init path
- AI-agent files and hooks are package-aligned with description as a Claude Code team harness
- No credential harvesting or exfiltration found; env vars are used for repo path/config templates
- MCP config is copied only as .claude/mcp-servers.example.json and README says manual merge is required
- knowledge.js child_process use is tied to explicit publish/session commands, validation, git workflow
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgInstall-time source drops package-supplied AI-agent/MCP control files or instructions.
scripts/install.jsView on unpkg · L1Hardcoded password in rules/common/security.md
rules/common/security.mdView on unpkg · L62