minimal-forge-work-pack-sync@0.1.17
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiSource inspection shows package-aligned Forge synchronization and usage reporting, with credentials selected for the configured origin. The scanner's credential-transfer hint reflects authenticated requests to that same configured service; no concrete attack behavior was identified.
Decision evidence
public snapshot- package.json points to dist/index.js and defines no install lifecycle hooks.
- The plugin requires a configured Forge origin and restricts it to HTTPS or loopback.
- It reads a Forge API key from the OpenCode auth entry keyed by that same origin.
- Startup uses that origin for manifest synchronization and sends the corresponding API key.
- Usage evidence is sent only after a skill tool uses a Forge-managed pack, and goes to that origin.
- Configuration updates agent and command entries tracked by the sync state.
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.17.
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.17 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.