← Home

stoppable

npm Repository Homepage
9
Versions
—
License
No
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

boneskullgergelykehunterloftis

Keywords

servernetconnectsocketconnectionstopclosedisconnectdisconnectionhttphttpstcp

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate 2018 maintainer transition to boneskull (well-known Node.js contributor, mocha maintainer, 42 approved pkgs). ai
maintainer-change maintainer-added AI (maintainer-change): boneskull and gergelyke added as maintainers in 2018; boneskull is a trusted, long-standing npm publisher. ai
provenance no-provenance AI (provenance): stoppable is a 9-year-old, 5M downloads/week package published long before Sigstore provenance was available. Absence of attestation is expected and not a risk signal for this package. ai
phantom-deps phantom-dep:awaiting AI (phantom-deps): awaiting is listed as a runtime dependency and used in perf/test tooling; phantom-dep flag is a false positive for this package's usage pattern. ai

Versions (showing 9 of 9)

Version Deps Published
1.1.0 0 / 7
1.0.7 0 / 7
1.0.6 0 / 8
1.0.5 0 / 9
1.0.4 1 / 8
1.0.3 1 / 7
1.0.2 1 / 7
1.0.1 1 / 7
1.0.0 1 / 7

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

2 findings
HIGH Publisher changed: hunterloftis → boneskull (on 2018-04-09) provenance

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

2 findings
HIGH Publisher changed: hunterloftis → gergelyke (on 2017-12-15) provenance

This version was published by a different npm account than previous versions on 2017-12-15. 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.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.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.

v1.0.0

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.