← Home

stack-utils

npm Repository Homepage

Captures and cleans stack traces

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

jamestalmageisaacs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate transfer from jamestalmage to isaacs (highly trusted npm maintainer) as part of tapjs ecosystem consolidation. ai
maintainer-change maintainer-added AI (maintainer-change): isaacs is a highly trusted publisher; addition as maintainer is a legitimate ecosystem transfer. ai
provenance no-provenance AI (provenance): Published in 2017 before Sigstore provenance existed; not actionable. ai

Versions (showing 18 of 18)

Version Deps Published
2.0.6 1 / 7
2.0.5 1 / 7
2.0.4 2 / 6
2.0.3 1 / 6
2.0.2 1 / 6
2.0.1 1 / 6
2.0.0 1 / 6
1.0.5 1 / 6
1.0.4 1 / 6
1.0.3 1 / 6
1.0.2 0 / 7
1.0.1 0 / 7
1.0.0 0 / 7
0.4.0 0 / 9
0.3.0 0 / 9
0.2.0 0 / 5
0.1.0 0 / 5
0.0.1 0 / 5

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.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.5

1 finding
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. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

2 findings
HIGH Publisher changed: jamestalmage → isaacs (on 2017-02-02) provenance

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