execSync
1
Versions
—
License
Yes
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
mgutz
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): Install script compiles/selects native shell.node binary — standard native addon build pattern for this package's purpose of providing synchronous shell execution. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Bundled .node binaries are prebuilt native addons for Windows platforms, consistent with this package's documented purpose of wrapping synchronous shell execution via native code. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in install.js solely to invoke the native addon build process; not a malicious use — consistent with the package's core functionality. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.2 | 1 / 2 |
v1.0.2
3 findings
HIGH
Package has 'install' script
install-scripts
Script: node install.js
HIGH
Bundled binary files (2)
npm-metadata
Package contains compiled binaries that could be backdoors: • win32/v0.10/shell.node • win32/v0.8/shell.node
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.