← Home

partof

npm Repository Homepage
2
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

thenativeweb-admingolorodenyeldirnhummeldotkuro

Keywords

objectmatchsubset

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change reflects org admin account takeover of thenativeweb packages; consistent with repo URL and contributor list. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are thenativeweb org members; consistent with legitimate org transition. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers part of same org transition; no malicious signal. ai

Versions (showing 2 of 2)

Version Deps Published
3.0.7 0 / 3
1.0.0 0 / 3

v3.0.7

2 findings
HIGH Publisher changed: goloroden → thenativeweb-admin (on 2021-08-24) provenance

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