registry / @extenshi/cli / 0.16.0
@extenshi/cli@0.16.0
Pre-publish security scanner for browser extensions
AI Security Review
scanned 26d ago · by lpm-firewall-aiSource inspection found an explicit consent gate before the postinstall telemetry request, and the CLI entrypoint exposes the advertised extension-scanning command. The inspected behavior does not establish a concrete attack surface.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The postinstall hook runs during installation; it exits before network activity unless telemetry is explicitly enabled in the Extenshi configuration.
Impact
No credential harvesting, unrelated control-surface mutation, or destructive behavior was identified in the inspected sources.
Mechanism
After consent, the hook may send the package version and coarse runtime details with an anonymous install identifier to the configured telemetry host.
AI rationale
Source inspection found an explicit consent gate before the postinstall telemetry request, and the CLI entrypoint exposes the advertised extension-scanning command. The inspected behavior does not establish a concrete attack surface.
Evidence
package.jsondist/cli.jsscripts/postinstall.cjs
Network endpoints1
eu.i.posthog.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest runs a postinstall script and exposes the CLI through dist/cli.js.
- The CLI provides an explicit command to scan browser extension artifacts.
- The postinstall ping exits unless telemetry is explicitly recorded as true.
- The postinstall payload sends installation telemetry through a configurable host after the consent gate; no credential collection or consumer-project mutation was identified.
Evidence against
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.16.0.
See all versions of @extenshi/cli for other recorded verdicts.
- Review the evidence and your use of @extenshi/cli@0.16.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.