← Home

segfault-handler

npm Repository Homepage

catches SIGSEGV and prints diagnostic information

6
Versions
BSD-3-Clause
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

ddopsonno9rfeng

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): kneth (Kenneth Geisshirt) is listed as the package author and contributor in package.json; this is a legitimate maintainer transition, not a hostile takeover. ai
install-scripts install-script:install AI (install-scripts): node-gyp rebuild is the standard native addon compilation step for this C++ binding; stable and expected for every version of this package. ai
phantom-deps phantom-dep:nan AI (phantom-deps): nan is a native C++ build-time dependency used by node-gyp; it is not imported in JS and this is expected for all versions of this native addon. ai

Versions (showing 6 of 6)

Version Deps Published
1.3.0 2 / 0
1.2.0 2 / 0
1.1.0 2 / 0
1.0.1 2 / 0
0.2.3 2 / 0
0.2.1 1 / 0

v1.3.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.2.0

2 findings
HIGH Publisher changed: no9 → kneth (on 2019-05-18) provenance

This version was published by a different npm account than previous versions on 2019-05-18. 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.

v1.1.0

2 findings
HIGH Publisher changed: no9 → kneth (on 2019-04-30) provenance

This version was published by a different npm account than previous versions on 2019-04-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.

v1.0.1

2 findings
HIGH Publisher changed: rfeng → no9 (on 2018-05-17) provenance

This version was published by a different npm account than previous versions on 2018-05-17. 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.

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
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.