← Home

level-iterator-stream

npm Repository Homepage

Turn an abstract-leveldown iterator into a readable stream

16
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

vweeversjuliangruberralphtheninja

Keywords

level

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Both vweevers and ralphtheninja are known Level org maintainers; legitimate maintainer rotation within the same GitHub org. ai
provenance no-provenance AI (provenance): Published in 2018 before Sigstore provenance existed; expected for this era of packages. ai

Versions (showing 16 of 16)

Version Deps Published
5.0.0 2 / 13
4.0.2 3 / 12
4.0.1 3 / 9
4.0.0 3 / 6
3.0.1 3 / 4
3.0.0 3 / 4
2.0.3 3 / 4
2.0.2 3 / 4
2.0.1 3 / 4
2.0.0 3 / 4
1.3.1 4 / 5
1.3.0 4 / 5
1.2.0 4 / 5
1.1.1 3 / 4
1.1.0 3 / 4
1.0.0 3 / 4

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

1 finding
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
INFO No provenance attestation provenance

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

INFO Publisher changed: ralphtheninja → vweevers (on 2019-03-30) provenance

[Accepted risk] 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.

v4.0.0

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

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