@andy-toolforge/content-operations
Toolforge domain: content operations — research, plan, create, distribute, analyze
This report shows the evidence for @andy-toolforge/content-operations@1.0.1. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection confirms unconsented npm lifecycle mutation of a project AI-agent skill surface, which matches the firewall policy for ai_agent_control_hijack. No additional credential theft or exfiltration was found, but those are not required for this block category.
Decision evidence
public snapshot- package.json runs postinstall: node skills/postinstall.js
- skills/postinstall.js uses process.cwd() and creates .opencode/skills during npm install
- postinstall links or copies all package skill .md files into that agent skill directory
- Dropped skills contain package-supplied OpenCode-style skill frontmatter and instructions
- No child_process, eval/vm/Function, native binary loading, or credential harvesting found
- No exfiltration endpoint found; runtime network is limited to user-supplied browserManager URL and LLMClient calls
- lib/index.js only exports content operation classes
- mcp-tools.js registers a package-aligned content research tool and requires code only in handler
Source & flagged code
3 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.
skills/postinstall.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to @andy-toolforge/content-operations@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @andy-toolforge/content-operations@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.