minimal-forge-work-pack-sync@0.1.19
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe scanner’s credential-transfer finding corresponds to Forge API requests using a key associated with the configured Forge origin. The inspected source shows no unrelated recipient or other concrete attack behavior.
Decision evidence
public snapshot- The manifest exposes dist/index.js as the package entrypoint and has no lifecycle scripts.
- The plugin accepts a Forge origin only over HTTPS or loopback HTTP, and rejects URL credentials, query strings, fragments, and non-root paths.
- The API key is read from OpenCode authentication data for that same Forge origin and must have the expected well-known credential type and key.
- Skill usage reports are sent to that Forge origin and contain event data; the caller limits reporting to use of a Forge-managed skill.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L2613A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
Findings
Affected versions and remediation
This report applies to minimal-forge-work-pack-sync@0.1.19.
See all versions of minimal-forge-work-pack-sync for other recorded verdicts.
- Review the evidence and your use of minimal-forge-work-pack-sync@0.1.19 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.