@andy-toolforge/coding-support
Toolforge domain: Code analysis tools — line counting, dead code detection, dependency graphs, complexity reports
This report shows the evidence for @andy-toolforge/coding-support@1.0.2. 3 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms unconsented postinstall mutation of a project-level OpenCode skill directory, which matches the firewall block policy for broad AI-agent control-surface writes. No network exfiltration or remote code execution was found, but the install-time agent configuration mutation is sufficient for block. Product guard normalized a concrete AI-agent control hijack publish_block to the blockable dangerous-capability shape.
Decision evidence
public snapshot- package.json defines postinstall: node skills/postinstall.js.
- skills/postinstall.js runs at install time and creates .opencode/skills under process.cwd().
- postinstall links or copies package markdown skill files into the project AI-agent skill directory without an explicit user command.
- Dropped skills instruct AI code review/refactoring behavior, making this an AI-agent control-surface mutation.
- No network APIs, HTTP endpoints, or credential harvesting found in reviewed files.
- No child_process, eval/vm/Function, native binary loading, destructive deletion, or persistence beyond dropped .opencode skill files.
- Runtime library lib/codebase-analyzer.js is aligned with advertised code analysis features and reads user-selected files/globs.
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 unpkgFindings
Affected versions and remediation
This report applies to @andy-toolforge/coding-support@1.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @andy-toolforge/coding-support@1.0.2. 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.