Evidence for AI clean decision
- The postinstall hook fetches versioned native assets from the project’s GitHub releases and checks their SHA-256 against the release manifest.
- The GitHub OAuth flow is triggered by the explicit `jsql star` command; the CLI describes it as checking whether the user starred the project.
- The optional token check sends a GitHub token to `api.github.com` to check the project’s star status.
- The worker compiles user-registered functions in a VM sandbox by default; unsafe host access requires an explicit environment setting.
Evidence against
- The package does have a postinstall hook that performs native asset setup.
- The explicit star-confirmation flow uses `auth.vexify.top` for OAuth.
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 59 files · 1.32 MB of source
6 external domains referenced
- api.github.com
- auth.vexify.top
- github.com
- registry-beta.vexify.top
- registry.npmjs.org
- rustup.rs