claude-code-templates@1.29.7
Component templates and tracking system for Claude Code
AI Security Review
scanned 24d ago · by lpm-firewall-aiStatic inspection found an explicit user-invoked agent installation capability that writes files into `.claude/agents`, so this merits a warning under the agent capability policy. The inspected source does not establish covert execution, credential theft, or malicious install-time behavior.
Decision evidence
public snapshot- The Cloudflare sandbox flow can install selected agent definitions into the project’s `.claude/agents` directory from the package publisher’s GitHub repository.
- The install is reachable when the user invokes the Cloudflare sandbox flow and supplies agent components; source inspection found no npm install lifecycle hook.
- The manifest exposes the CLI and main module, and its only lifecycle script is `prepublishOnly`, which checks version synchronization.
- The session-sharing path validates imported conversation IDs before writing session files; the local API proxy restricts requests to loopback hosts without an Origin header.
- The agent-file installation is tied to selected components in an explicit CLI flow, rather than an npm installation hook.
Source & flagged code
9 flaggedPackage source references child process execution.
cli-tool/components/sandbox/docker/execute.jsView on unpkg · L10Findings
Affected versions and remediation
This report applies to claude-code-templates@1.29.7.
See all versions of claude-code-templates for other recorded verdicts.
- Review the evidence and your use of claude-code-templates@1.29.7 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.