minimal-forge-work-pack-sync@0.1.36
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe scanner’s credential-transfer hints resolve to Forge synchronization and a manifest-selected, HTTPS-only gateway. The package has no lifecycle hook, and the recovery utility’s reconnect flow is user-selected.
Decision evidence
public snapshot- package.json points the package entrypoint to dist/index.js and declares no lifecycle scripts.
- The entrypoint sends the Forge API key to the configured Forge origin to fetch its manifest.
- The manifest-selected gateway must be an HTTPS origin without credentials, a port, path, query, or fragment.
- The separate recovery utility fetches the manifest from the Forge origin; its reconnect path is an explicit action.
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.36.
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.36 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.