minimal-forge-work-pack-sync@0.1.39
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiSource inspection did not substantiate the scanner's claim of a fixed unofficial credential gateway. The observed credential transfers support the package's configured Forge synchronization and user-selected recovery behavior.
Decision evidence
public snapshot- The manifest points to dist/index.js and declares no lifecycle scripts.
- The active entrypoint loads credentials for the configured Forge origin and sends them to that origin's /sync/manifest endpoint.
- The model gateway comes from the Forge manifest and must be an HTTPS origin; the source contains no fixed unofficial gateway.
- The separate recovery helper enrolls again only after the user selects its reenrollment 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.39.
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.39 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.