← Home

levelup

Fast & simple storage - a Node.js-style LevelDB wrapper

51
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

vweeversrvaggralphtheninja

Keywords

levelleveldbstreamdatabasedbstorestoragejson

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): vweevers is a known Level ecosystem maintainer with 739 approved packages; the ralphtheninja→vweevers transition is a documented legitimate handoff within the Level GitHub org. ai
maintainer-change maintainer-removed AI (maintainer-change): juliangruber's removal is consistent with the known Level org maintainer transition; no hostile takeover indicators present. ai

Versions (showing 51 of 82)

View all versions
Version Deps Published
5.1.1 6 / 22
5.1.0 6 / 22
5.0.1 6 / 23
5.0.0 6 / 24
4.4.0 5 / 24
4.3.2 5 / 24
4.3.1 5 / 24
4.3.0 5 / 24
4.2.0 4 / 24
4.1.0 4 / 23
4.0.2 4 / 23
4.0.1 4 / 21
4.0.0 4 / 20
3.1.1 4 / 24
3.1.0 4 / 23
3.0.1 4 / 17
3.0.0 4 / 18
2.0.2 4 / 18
2.0.1 4 / 19
2.0.0 4 / 19
1.3.9 7 / 16
1.3.8 7 / 15
1.3.7 7 / 13
1.3.6 7 / 13
1.3.5 7 / 12
1.3.4 7 / 12
1.3.3 7 / 12
1.3.2 7 / 12
1.3.1 7 / 12
1.3.0 7 / 12
1.2.1 7 / 11
1.2.0 7 / 11
1.1.1 7 / 11
1.1.0 7 / 12
1.0.0 7 / 12
0.19.1 7 / 17
0.19.0 7 / 16
0.18.6 7 / 16
0.18.5 7 / 16
0.18.4 7 / 16
0.18.3 7 / 16
0.18.2 8 / 16
0.18.1 8 / 16
0.18.0 8 / 16
0.17.0 8 / 16
0.16.0 7 / 16
0.15.0 7 / 16
0.14.0 7 / 16
0.13.0 7 / 15
0.12.0 7 / 15
0.11.0 7 / 15

v5.1.1

1 finding
LOW No provenance attestation provenance

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

v5.1.0

1 finding
LOW No provenance attestation provenance

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

v5.0.1

1 finding
LOW No provenance attestation provenance

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

v5.0.0

1 finding
LOW No provenance attestation provenance

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

v4.4.0

1 finding
LOW No provenance attestation provenance

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

v4.3.2

1 finding
LOW No provenance attestation provenance

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

v4.3.1

1 finding
LOW No provenance attestation provenance

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

v4.3.0

1 finding
LOW No provenance attestation provenance

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

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.2

2 findings
HIGH Publisher changed: ralphtheninja → vweevers (on 2019-06-08) provenance

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

v4.0.1

2 findings
HIGH Publisher changed: ralphtheninja → vweevers (on 2019-03-30) provenance

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

v4.0.0

1 finding
LOW No provenance attestation provenance

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