@plannotator/opencode@0.28.40
Plannotator plugin for OpenCode - interactive plan review with visual annotation
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package automatically installs its own OpenCode commands and skill into user configuration during postinstall. This is an agent-extension lifecycle risk, but the inspected runtime credential transport targets localhost and no malicious exfiltration was identified.
Decision evidence
public snapshot- The package runs scripts/postinstall.cjs automatically through its postinstall lifecycle script.
- For an installed package under node_modules, postinstall copies command stubs and a skill into the OpenCode user config directory.
- The destination is <XDG_CONFIG_HOME or ~/.config>/opencode, outside the package directory.
- The runtime bridge sends its bearer token and request data only to a loopback address, 127.0.0.1.
- The postinstall copies the package's own OpenCode commands and Plannotator skill; no unrelated payload or external contact was identified.
- The server's credential-bearing request is addressed to a local service, not an external host.
Source & flagged code
5 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @plannotator/opencode@0.28.40.
See all versions of @plannotator/opencode for other recorded verdicts.
- Review the evidence and your use of @plannotator/opencode@0.28.40 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.