loglevelnext
A modern logging library for Node.js and modern browsers that provides log level mapping to the console
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 | missing-githead | AI (provenance): Publisher is the original long-standing author; gitHead absence reflects a build toolchain change (tsup migration), not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Many established packages lack Sigstore provenance; informational only, not a security risk for this trusted publisher. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 0 / 15 | |
| 5.0.6 | 0 / 14 | |
| 5.0.5 | 0 / 14 | |
| 5.0.4 | 0 / 14 | |
| 5.0.3 | 0 / 14 | |
| 5.0.2 | 0 / 14 | |
| 5.0.1 | 0 / 14 | |
| 5.0.0 | 0 / 14 | |
| 4.0.1 | 0 / 9 | |
| 3.0.1 | 0 / 12 | |
| 3.0.0 | 0 / 12 | |
| 2.0.1 | 2 / 20 | |
| 2.0.0 | 2 / 20 | |
| 1.0.5 | 2 / 20 | |
| 1.0.4 | 0 / 20 | |
| 1.0.3 | 0 / 19 | |
| 1.0.2 | 0 / 19 | |
| 1.0.1 | 0 / 19 | |
| 1.0.0 | 0 / 19 | |
| 0.0.1 | 0 / 0 |
v6.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shellscape.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.