minimal-forge-work-pack-sync@0.1.18
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe scanner flags correspond to authenticated Forge synchronization and limited usage reporting. Source ties credentials and requests to the configured, validated Forge origin, with no confirmed malicious behavior.
Decision evidence
public snapshot- package.json points to dist/index.js and declares no lifecycle script.
- The OpenCode plugin uses its configured Forge origin to start synchronization.
- Credential lookup selects the Forge API key stored under that same origin, and the origin must use HTTPS or loopback HTTP.
- Evidence reporting is limited to session kinds and Forge-managed skill use; invocation events contain an aggregate kind, slug, day, and count.
- Work-pack archive URLs must match the Forge origin before the API key is sent.
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.18.
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.18 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.