Evidence for AI clean decision
- The postinstall downloads a versioned native module from the project’s GitHub releases and refuses to download an unverified binary.
- GitHub credentials are sent to api.github.com for the repository star check, which the CLI reaches only with the explicit --token-check option.
- The default CLI nag reads local config and prints a visible link; its startup path does not make a network request.
- SQLite UDF code is supplied by the caller and runs in a restricted VM by default; unsafe execution requires an explicit environment setting.
Evidence against
- The package has a postinstall hook that downloads a native binary, but it uses the project’s release host and verifies the asset checksum.
- The package reads GitHub credentials, but the inspected flow sends them to GitHub’s API only when the user explicitly requests a token check. The separate OAuth flow is also explicitly invoked.
Behavioral surface
SourceChild process · Crypto · Dynamic require · Environment variables · Eval · Filesystem · Native bindings · Network · Shell
Supply chainHigh entropy strings · URL strings
ManifestNo manifest risk signals triggered.
Scanned 61 files · 1.50 MB of source
5 external domains referenced
- api.github.com
- auth.vexify.top
- github.com
- registry-beta.vexify.top
- registry.npmjs.org