registry / @extenshi/cli / 0.15.1
@extenshi/cli@0.15.1
Pre-publish security scanner for browser extensions
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe package has a postinstall hook, but its telemetry path is guarded by recorded user consent and sends limited installation metadata. The inspected CLI behavior is consistent with its scanner and update-check functionality, with no concrete attack surface established.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installing the package with telemetry already enabled, or running the CLI when its update check is due.
Impact
No malicious effect was established from the inspected behavior.
Mechanism
The install hook sends an installation event; the CLI update check fetches the latest version from npm.
AI rationale
The package has a postinstall hook, but its telemetry path is guarded by recorded user consent and sends limited installation metadata. The inspected CLI behavior is consistent with its scanner and update-check functionality, with no concrete attack surface established.
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the CLI and runs scripts/postinstall.cjs after installation.
- The postinstall exits unless telemetry consent is recorded as true; it also skips workspace installs and CI.
- The postinstall sends an installation event with package version and coarse runtime metadata; no credentials or package contents are included in the payload.
- The CLI provides a browser extension scanning command, and its update check reads the npm registry.
Evidence against
- The postinstall can send telemetry during installation after consent, and its destination can be overridden with EXTENSHI_POSTHOG_HOST.
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.15.1.
See all versions of @extenshi/cli for other recorded verdicts.
- Review the evidence and your use of @extenshi/cli@0.15.1 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.