← Home

kexec

Replace your Node.js process with another process. Like Ruby exec.

13
Versions
MIT
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

smblottjprichardson

Keywords

execspawnprocesskexec

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): nan is the standard native addon abstraction library; its addition is consistent with kexec's purpose as a native Node.js process-replacement binding. ai
phantom-deps phantom-dep:nan AI (phantom-deps): nan is used via binding.gyp/node-gyp configuration, not direct require(); this is normal for native addon dependencies. ai
install-scripts install-script:install AI (install-scripts): node-gyp rebuild is the canonical install script for native Node.js addons; stable and expected for this package. ai
provenance publisher-changed AI (provenance): Publisher change from smblott to jp (jprichardson) occurred in 2014 and is a long-settled legitimate maintainer transition. ai

Versions (showing 13 of 13)

Version Deps Published
3.0.0 1 / 2
1.3.0 1 / 1
1.2.0 1 / 1
1.1.1 1 / 1
1.1.0 0 / 2
1.0.0 0 / 1
0.2.0 0 / 1
0.1.2 0 / 1
0.1.1 0 / 1
0.1.0 0 / 1
0.0.3 0 / 0
0.0.2 0 / 0
0.0.1 0 / 0

v3.0.0

2 findings
HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

3 findings
HIGH Package has 'install' script install-scripts

Script: node-gyp configure build

HIGH Publisher changed: smblott → jp (on 2014-12-30) provenance

This version was published by a different npm account than previous versions on 2014-12-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.