registry / @plannotator/opencode / 0.28.45
@plannotator/opencode@0.28.45
Plannotator plugin for OpenCode - interactive plan review with visual annotation
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe postinstall hook automatically writes the package’s own commands and skill into the user’s OpenCode configuration, potentially replacing existing files. This matches the package’s purpose but is automatic extension setup, so it merits a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The postinstall hook runs for an installed package under node_modules unless the PLANNOTATOR_OPENCODE_POSTINSTALL override disables copying.
Impact
Changes OpenCode commands and skill files outside the package directory without an explicit setup command.
Mechanism
Copies command markdown files and the package skill into the OpenCode config directory; existing destination files may be overwritten.
AI rationale
The postinstall hook automatically writes the package’s own commands and skill into the user’s OpenCode configuration, potentially replacing existing files. This matches the package’s purpose but is automatic extension setup, so it merits a warning rather than a block.
Evidence
package.jsonscripts/postinstall.cjs${XDG_CONFIG_HOME:-~/.config}/opencode/commands/*.md${XDG_CONFIG_HOME:-~/.config}/opencode/skills/plannotator/SKILL.md
Decision evidence
public snapshotAI called this Suspicious at 92.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The package runs scripts/postinstall.cjs during postinstall.
- Unless disabled by an environment override, the script copies assets when installed under node_modules.
- The script copies package command files and its skill into the user’s OpenCode config, potentially replacing files at those destinations.
Evidence against
- The copied files are the package’s own OpenCode commands and skill, matching its plugin purpose.
- The observed runtime fetches target 127.0.0.1 for the local Inbox service; no unrelated data collection was identified.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedTelemetryUrlStrings
Source & flagged code
6 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdiagram-engine/engine.jsView file
1function gc(e,t){for(var n=0;n<t.length;n++){const r=t[n];if(typeof r!="string"&&!Array.isArray(r)){for(const o in r)if(o!=="default"&&!(o in e)){const s=Object.getOwnPropertyDescr...
L2: `);let n=t.length;for(;n>0&&(t[n-1]??"").trim()==="";)n-=1;let r=1;for(;r<=n&&(t[r-1]??"").trim()==="";)r+=1;return n===0||r>n?null:[r,n]}function Rc(e){for(const t of e.split(`
Medium
Findings
1 Critical2 High6 Medium7 Low
CriticalHardcoded Runtime Data Exfiltrationdist/index.js
HighInstall Time Lifecycle Scriptspackage.json
HighPrevious Version Dangerous Deltadist/server.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirediagram-engine/engine.js
MediumNetwork
MediumEnvironment Vars
MediumOversized Source Filediagram-engine/mermaid.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEval
LowFilesystem
LowHigh Entropy Strings
Low
Affected versions and remediation
This report applies to @plannotator/opencode@0.28.45.
See all versions of @plannotator/opencode for other recorded verdicts.
- Review the evidence and your use of @plannotator/opencode@0.28.45 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.