registry / @plannotator/opencode / 0.27.18
@plannotator/opencode@0.27.18
Plannotator plugin for OpenCode - interactive plan review with visual annotation
AI Security Review
scanned 28d ago · by lpm-firewall-aiSource inspection found first-party OpenCode command and skill setup in postinstall and ordinary package-local runtime loading and CLI invocation in the server. No concrete malicious behavior was established, so this is clean.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation triggers the postinstall hook; plugin use can launch the configured Plannotator CLI.
Impact
The observed install-time effect is first-party plugin setup; no concrete credential theft, exfiltration, or unrelated control hijack was established.
Mechanism
The hook copies packaged Markdown files into OpenCode configuration directories, while the server imports a package-local runtime and invokes the CLI.
AI rationale
Source inspection found first-party OpenCode command and skill setup in postinstall and ordinary package-local runtime loading and CLI invocation in the server. No concrete malicious behavior was established, so this is clean.
Evidence
package.jsondist/server.js
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook copies the package’s command and skill files into OpenCode configuration directories.
- The server launches the configured Plannotator CLI with request input through standard input.
- Embedded runtime loading imports the package-local embedded.js file.
Evidence against
- The manifest identifies this as an OpenCode plugin, and its install hook only copies its own commands and skill into OpenCode configuration.
- Inspected server execution and dynamic import paths are limited to launching the Plannotator CLI and loading a package-local runtime; no concrete attack behavior was found.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedpackage.jsonView file
•scripts.postinstall = mkdir -p ${XDG_CONFIG_HOME:-$HOME/.config}/opencode/commands && cp ./commands/*.md ${XDG_CONFIG_HOME:-$HOME/.config}/opencode/commands/ 2>/dev/null || true; mkdir -p ${XDG_CONFIG_H...
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = mkdir -p ${XDG_CONFIG_HOME:-$HOME/.config}/opencode/commands && cp ./commands/*.md ${XDG_CONFIG_HOME:-$HOME/.config}/opencode/commands/ 2>/dev/null || true; mkdir -p ${XDG_CONFIG_H...
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/server.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @plannotator/opencode@0.27.14
matchedIdentity = npm:QHBsYW5ub3RhdG9yL29wZW5jb2Rl:0.27.14
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
Findings
2 High6 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighPrevious Version Dangerous Deltadist/server.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/server.js
MediumNetwork
MediumEnvironment Vars
MediumOversized Source Filedist/embedded.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @plannotator/opencode@0.27.18.
See all versions of @plannotator/opencode for other recorded verdicts.
- Review the evidence and your use of @plannotator/opencode@0.27.18 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.