minimal-forge-work-pack-sync@0.1.24
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiSource inspection supports the scanner’s network and credential indicators as package-aligned Forge operations: the endpoint is configured by the plugin, telemetry concerns managed work-pack activity, and archive downloads are constrained to the Forge origin. No concrete attack surface was established.
Decision evidence
public snapshot- The manifest exposes dist/index.js as the package entrypoint and declares no lifecycle scripts.
- The plugin runs startup synchronization for its configured Forge origin.
- Usage reporting is limited to Forge-managed work-pack invocations and sends to that configured Forge origin.
- Downloaded work-pack archives are restricted to the same origin as the configured Forge server.
- Runtime health probes accept only loopback URLs.
Source & flagged code
4 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.
dist/index.jsFindings
Affected versions and remediation
This report applies to minimal-forge-work-pack-sync@0.1.24.
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.24 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.