level-errors
Error types for levelup
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): vweevers is a long-standing Level org maintainer (729 approved packages, first seen 3117 days ago); this is a legitimate org-level maintainer transition, not a takeover. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 0 / 7 | |
| 3.0.0 | 1 / 9 | |
| 2.0.1 | 1 / 7 | |
| 2.0.0 | 1 / 2 | |
| 1.1.2 | 1 / 2 | |
| 1.1.1 | 1 / 1 | |
| 1.1.0 | 1 / 1 | |
| 1.0.5 | 1 / 1 | |
| 1.0.4 | 1 / 1 | |
| 1.0.3 | 1 / 1 | |
| 1.0.2 | 1 / 1 | |
| 1.0.1 | 1 / 1 | |
| 1.0.0 | 1 / 0 |
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2019-04-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.