@plannotator/opencode@0.28.39
Plannotator plugin for OpenCode - interactive plan review with visual annotation
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe reviewed lifecycle code only copies the package’s command and skill assets, and the flagged token-bearing requests target a loopback Inbox service. The download-and-run string is an installation suggestion shown when the CLI is missing, not an automatically executed command.
Decision evidence
public snapshot- The package exposes OpenCode plugin entry points for its two supported host versions.
- The postinstall hook copies the package’s command stubs and skill into OpenCode’s config directory.
- The flagged credential-bearing request sends to a loopback address and uses a token read from the local Inbox registry.
- Plugin setup registers OpenCode commands and optional Inbox tools; no external credential receiver was identified.
- The package runs a postinstall hook that writes files outside the package directory when installed under node_modules.
- The plugin uses local filesystem and process environment data to configure its OpenCode and Inbox integrations.
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.39.
See all versions of @plannotator/opencode for other recorded verdicts.
- Review the evidence and your use of @plannotator/opencode@0.28.39 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.