@plannotator/opencode@0.28.49
Plannotator plugin for OpenCode - interactive plan review with visual annotation
AI Security Review
scanned 10h ago · by lpm-firewall-aiThe package’s postinstall can install its own commands and skill into the user’s OpenCode config, an automatic extension setup that merits a warning. The flagged runtime credential flows inspected here use loopback endpoints, and I found no concrete exfiltration behavior.
Decision evidence
public snapshot- The postinstall hook runs a Node script that copies package commands and its Plannotator skill into the OpenCode config directory.
- The script copies assets when the package is installed under node_modules; it also supports an explicit environment override.
- The flagged credential-bearing requests target 127.0.0.1 and use a token read from the local Inbox registry.
- The manifest identifies this as a Plannotator OpenCode plugin, and the copied command is for explicitly requested code review.
- The package’s runtime requests inspected here use loopback addresses; no unrelated external receiver was identified.
Source & flagged code
6 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.49.
See all versions of @plannotator/opencode for other recorded verdicts.
- Review the evidence and your use of @plannotator/opencode@0.28.49 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.