minimal-forge-work-pack-sync@0.1.26
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 map to functional Forge reporting: the destination comes from Forge credentials and the reported events are limited usage metadata. The manifest has no install lifecycle hook, and the inspected code does not establish an attack surface.
Decision evidence
public snapshot- package.json points to dist/index.js and declares no lifecycle scripts.
- The exported OpenCode plugin records session event types and counts of Forge-managed work-pack invocations.
- Telemetry sends those events to the Forge base URL from the existing Forge credentials file; no unrelated recipient or collection of prompts, files, or credentials was identified.
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.26.
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.26 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.