minimal-forge-work-pack-sync@0.1.25
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe scanner’s credential and network hints correspond to Forge synchronization and reporting in the plugin entrypoint. The inspected source binds the credential to the configured Forge origin, validates that origin, and shows no install-time trigger or unrelated recipient.
Decision evidence
public snapshot- The manifest exposes a plugin entrypoint and defines no lifecycle scripts.
- The plugin validates its configured Forge origin and only permits HTTPS, apart from loopback HTTP.
- It reads the Forge credential associated with that same origin and sends it to that origin’s sync endpoint.
- The server health probe accepts only loopback hosts.
- No package install hook or unrelated credential recipient was identified in the inspected source.
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.25.
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.25 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.