registry / @plannotator/opencode / 0.27.15
@plannotator/opencode@0.27.15
Plannotator plugin for OpenCode - interactive plan review with visual annotation
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe install-time configuration writes are first-party OpenCode command and skill setup consistent with the package's plugin role. Inspected executable excerpts establish no concrete malicious behavior, credential exposure, or attack surface.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation runs postinstall; runtime behavior starts when the OpenCode plugin invokes an action.
Impact
This adds first-party OpenCode commands and skill files and enables plan review; inspected excerpts establish no concrete attack effect.
Mechanism
The hook copies bundled command and skill files into OpenCode directories. Server actions load the embedded module, run the configured CLI, and save review edits for the host.
AI rationale
The install-time configuration writes are first-party OpenCode command and skill setup consistent with the package's plugin role. Inspected executable excerpts establish no concrete malicious behavior, credential exposure, or attack surface.
Evidence
package.jsondist/server.js
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook copies package command and skill files into OpenCode's user configuration directories.
- The server loads its bundled embedded module and launches the configured Plannotator CLI for plugin actions.
- Plan edits are saved to a backing file and passed to the host review function.
Evidence against
- The lifecycle hook installs first-party OpenCode commands and a Plannotator skill; inspected source shows no credential collection or transmission.
- The inspected server excerpts support the package's plan review and annotation purpose; they show no malicious payload execution.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
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 Medium5 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
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @plannotator/opencode@0.27.15.
See all versions of @plannotator/opencode for other recorded verdicts.
- Review the evidence and your use of @plannotator/opencode@0.27.15 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.