← Home

get-npm-tarball-url

npm Repository Homepage

Create the tarball URL of a npm package

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

zkochan

Keywords

npmurltarball

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established package from trusted pnpm maintainer; lack of Sigstore provenance is informational, not a risk signal. ai
provenance missing-githead AI (provenance): Publisher environment change for a 9-year-old package by its original author; benign metadata difference. ai
publish-pattern dormant-publish AI (publish-pattern): Small utility in the pnpm org by a trusted maintainer; long dormancy is consistent with a stable, rarely-updated utility rather than account takeover. ai

Versions (showing 8 of 8)

Version Deps Published
2.1.0 0 / 6
2.0.3 0 / 5
2.0.2 1 / 5
2.0.1 1 / 5
2.0.0 0 / 4
1.0.1 0 / 4
1.0.0 0 / 4
0.0.0 0 / 4

v2.1.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zkochan.

LOW No provenance attestation provenance

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

v2.0.3

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zkochan.

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
INFO No provenance attestation provenance

[Accepted risk] 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.1

1 finding
INFO No provenance attestation provenance

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

v1.0.0

1 finding
INFO No provenance attestation provenance

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