registry / @extenshi/cli / 0.20.0
@extenshi/cli@0.20.0
Pre-publish security scanner for browser extensions
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe manifest’s automatic postinstall leads to telemetry code that requires an existing positive consent setting before sending its limited event. Inspected source does not establish malicious behavior, so the scanner’s suspicious labels do not warrant a warning.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation followed by the install hook finding recorded telemetry consent.
Impact
No confirmed attack surface was established; the inspected hook gates the request on recorded consent and does not send credentials or project contents.
Mechanism
The hook posts an anonymous install event and coarse package and runtime metadata to its configured telemetry host.
AI rationale
The manifest’s automatic postinstall leads to telemetry code that requires an existing positive consent setting before sending its limited event. Inspected source does not establish malicious behavior, so the scanner’s suspicious labels do not warrant a warning.
Evidence
package.jsonscripts/postinstall.cjsdist/cli.js
Network endpoints1
eu.i.posthog.com
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs a postinstall script automatically.
- The install ping proceeds only when the existing config records telemetry consent.
- The ping sends package and runtime metadata with an anonymous ID; the CLI entrypoint loads telemetry initialization.
Evidence against
- No inspected source showed collection of credentials, user files, or project contents in the install ping.
- The automatic ping is gated by recorded consent; no confirmed attack surface was established.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsTelemetryUrlStrings
NoLicense
Source & flagged code
5 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 unpkgdist/auto-update.jsView file
25try {
L26: const require = createRequire(import.meta.url);
L27: const pkg = require('../package.json');
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/auto-update.jsView on unpkg · L25Findings
3 High5 Medium7 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limiteddist/cli.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltadist/cli.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/auto-update.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @extenshi/cli@0.20.0.
See all versions of @extenshi/cli for other recorded verdicts.
- Review the evidence and your use of @extenshi/cli@0.20.0 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.