minimal-forge-work-pack-sync@0.1.43
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiSource inspection shows the credential requests are tied to the configured Forge origin, while the manifest gateway is used as the intended provider endpoint and restricted to HTTPS. The repair caller requires an explicit reenrollment selection; the scanner hints do not establish an unrelated credential recipient or malicious behavior.
Decision evidence
public snapshot- package.json selects dist/index.js as the package entrypoint and declares no lifecycle hook.
- Startup reads the Forge credential for the configured Forge origin and fetches the manifest from that origin.
- The manifest-provided gateway is restricted to an HTTPS origin, and its URL is used with the Forge API key as the provider endpoint.
- The repair flow reads its Forge origin, obtains a new key for that origin, and fetches its manifest with that key; its menu invokes this flow only for the explicit reenrollment choice.
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.43.
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.43 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.