minimal-forge-work-pack-sync@0.1.33
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found a plugin entrypoint without install hooks and usage reporting scoped to the configured Forge origin. The reviewed transfer uses Forge credentials associated with that origin and sends limited usage metadata, so no confirmed attack surface remains.
Decision evidence
public snapshot- The manifest points to a bundled plugin entrypoint and declares no install lifecycle hook.
- The plugin queues session events and work pack invocation counts, then sends them to the configured Forge origin.
- Saved Forge credentials are looked up under that same Forge origin; the reviewed transfer does not show prompt or file content being sent.
Source & flagged code
4 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.33.
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.33 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.