minimal-forge-work-pack-sync@0.1.46
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe plugin trusts a manifest-provided HTTPS gateway without checking that it belongs to the configured Forge service, then persists the Forge API key for use there. The source does not identify a fixed unrelated recipient, so this is a real credential-routing risk but not enough to establish malicious exfiltration.
Decision evidence
public snapshot- The package exports dist/index.js as its plugin entrypoint.
- At startup, the plugin reads Forge credentials, fetches a manifest, and takes the gateway URL from that manifest.
- Gateway validation accepts any HTTPS origin; it does not require the host to match the configured Forge service.
- The generated OpenCode provider config uses the manifest gateway as its base URL and reuses the Forge API key.
- The image tool sends that Forge key as a bearer token to the gateway host.
- The manifest itself is fetched from the configured Forge origin with redirects rejected.
- The gateway URL is supplied by the Forge manifest; the package source does not hard-code an unrelated gateway host.
- The credential involved is the Forge-specific key, not a discovered credential for another service.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L2615A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsFindings
Affected versions and remediation
This report applies to minimal-forge-work-pack-sync@0.1.46.
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.46 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.