minimal-forge-work-pack-sync@0.1.16
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe scanner's credential-transfer indicators resolve to Forge synchronization using the credential associated with the configured, HTTPS-validated Forge origin. The inspected source shows no unrelated recipient or other concrete attack behavior.
Decision evidence
public snapshot- The manifest exposes the package as an OpenCode plugin through dist/index.js.
- The plugin accepts its Forge origin through options and uses it to start synchronization.
- The origin parser requires HTTPS except for loopback and rejects credentials, query strings, fragments, and non-root paths.
- The startup sync retrieves a manifest and applies it using credentials for that Forge origin.
- The credential lookup requires a matching OpenCode well-known Forge authorization record.
- The embedded evidence reporter queues session event categories and sends them to the configured Forge origin.
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.16.
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.16 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.