← Home

level-packager

npm Repository Homepage

levelup package helper for distributing with an abstract-leveldown store

31
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): Legitimate maintainer transition within the Level org; vweevers is a well-known Level ecosystem maintainer with extensive track record. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance; informational only, no security concern. ai

Versions (showing 31 of 31)

Version Deps Published
6.0.1 2 / 7
6.0.0 2 / 9
5.1.1 2 / 7
5.1.0 2 / 7
5.0.3 2 / 7
5.0.2 2 / 7
5.0.1 2 / 7
5.0.0 2 / 6
4.0.1 2 / 6
4.0.0 2 / 2
3.1.0 2 / 3
3.0.0 2 / 3
2.1.1 2 / 3
2.1.0 2 / 3
2.0.2 2 / 2
2.0.1 2 / 2
2.0.0 2 / 2
1.2.1 1 / 2
1.2.0 1 / 2
1.1.0 1 / 2
1.0.0 1 / 2
0.19.7 1 / 2
0.19.6 1 / 0
0.19.5 1 / 0
0.19.4 1 / 0
0.19.3 1 / 0
0.19.2 1 / 0
0.19.1 1 / 0
0.19.0 1 / 0
0.18.0 1 / 0
0.17.0 1 / 1

v6.0.1

1 finding
LOW No provenance attestation provenance

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

v6.0.0

1 finding
LOW No provenance attestation provenance

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

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.3

1 finding
LOW No provenance attestation provenance

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

v5.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.

v5.0.1

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

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

v5.0.0

2 findings
HIGH Publisher changed: ralphtheninja → vweevers (on 2018-12-27) provenance

This version was published by a different npm account than previous versions on 2018-12-27. 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.