abstract-leveldown
An abstract prototype matching the LevelDOWN API
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): The ralphtheninja→vweevers transition is a documented 2018 Level org maintainer handoff. vweevers has 737 approved packages and 0 rejected; no compromise indicators. | ai | |
| provenance | no-provenance | AI (provenance): Package was published in 2018, predating npm/Sigstore provenance attestation. Not a meaningful risk signal for this package. | ai |
Versions (showing 51 of 78)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 6 / 8 | |
| 7.1.0 | 5 / 8 | |
| 7.0.0 | 5 / 10 | |
| 6.3.0 | 5 / 9 | |
| 6.2.3 | 5 / 9 | |
| 6.2.2 | 3 / 9 | |
| 6.2.1 | 3 / 9 | |
| 6.2.0 | 3 / 9 | |
| 6.1.1 | 2 / 9 | |
| 6.1.0 | 2 / 9 | |
| 6.0.3 | 2 / 9 | |
| 6.0.2 | 2 / 9 | |
| 6.0.1 | 2 / 8 | |
| 6.0.0 | 2 / 8 | |
| 5.0.0 | 1 / 5 | |
| 4.0.3 | 1 / 7 | |
| 4.0.2 | 1 / 7 | |
| 4.0.1 | 1 / 7 | |
| 4.0.0 | 1 / 4 | |
| 3.0.0 | 1 / 3 | |
| 2.7.2 | 1 / 3 | |
| 2.7.1 | 1 / 3 | |
| 2.7.0 | 1 / 3 | |
| 2.6.3 | 1 / 3 | |
| 2.6.2 | 1 / 3 | |
| 2.6.1 | 1 / 3 | |
| 2.6.0 | 1 / 3 | |
| 2.5.0 | 1 / 3 | |
| 2.4.1 | 1 / 3 | |
| 2.4.0 | 1 / 3 | |
| 2.3.1 | 1 / 3 | |
| 2.3.0 | 1 / 3 | |
| 2.2.2 | 1 / 3 | |
| 2.2.1 | 1 / 3 | |
| 2.2.0 | 1 / 3 | |
| 2.1.4 | 1 / 3 | |
| 2.1.3 | 1 / 3 | |
| 2.1.2 | 1 / 3 | |
| 2.1.1 | 1 / 3 | |
| 2.1.0 | 1 / 3 | |
| 2.0.3 | 1 / 3 | |
| 2.0.1 | 1 / 3 | |
| 2.0.0 | 1 / 3 | |
| 1.0.0 | 1 / 3 | |
| 0.12.4 | 1 / 3 | |
| 0.12.3 | 1 / 3 | |
| 0.12.2 | 1 / 3 | |
| 0.12.1 | 1 / 3 | |
| 0.12.0 | 1 / 3 | |
| 0.11.4 | 1 / 3 | |
| 0.11.3 | 1 / 3 |
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-10-20. 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.