minimal-forge-work-pack-sync@0.1.42
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe package entrypoint and inspected recovery flow support Forge synchronization and user-selected recovery. The source shows the saved key sent to the configured Forge service and no concrete unrelated recipient or attack behavior.
Decision evidence
public snapshot- The manifest points to dist/index.js and declares no lifecycle hooks.
- The manifest-reachable runtime restricts the configured gateway to an HTTPS origin without credentials, ports, paths, queries, or fragments.
- Recovery sends its saved Forge API key to the configured Forge base URL to fetch the sync manifest.
- The recovery flow uses that manifest to rebuild Forge configuration.
- A new enrollment runs only after the user selects the enrollment action; the normal recovery path requires the saved credential.
- Recovery errors are reported to the user.
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.42.
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.42 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.