minimal-forge-work-pack-sync@0.1.22
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe scanner’s credential and network matches correspond to authenticated Forge synchronization. Source inspection shows origin validation and a credential lookup keyed to that same origin, with no unrelated recipient identified.
Decision evidence
public snapshot- The manifest points to the bundled plugin entrypoint and declares no lifecycle scripts.
- The plugin accepts only HTTPS Forge origins, or HTTP loopback origins, and rejects credentials and URL extras.
- It retrieves a Forge API key only from the OpenCode auth record keyed by that same Forge origin.
- Startup synchronization uses that origin-scoped credential for the Forge manifest and sync reports.
- The bundle makes authenticated network requests and sends host and agent version information in sync reports; source ties these requests to the configured Forge origin.
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.
dist/index.jsFindings
Affected versions and remediation
This report applies to minimal-forge-work-pack-sync@0.1.22.
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.22 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.