debug-logfmt
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@jclem/logfmt2 | AI (dependencies): Small legitimate logfmt parsing lib; normal runtime dependency. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.4.13 | 3 / 15 | |
| 1.4.12 | 3 / 15 | |
| 1.4.11 | 3 / 16 | |
| 1.4.10 | 3 / 16 | |
| 1.4.9 | 3 / 16 | |
| 1.4.8 | 3 / 16 | |
| 1.4.7 | 3 / 16 | |
| 1.4.6 | 3 / 16 | |
| 1.4.5 | 3 / 16 | |
| 1.4.4 | 3 / 16 | |
| 1.4.3 | 3 / 16 | |
| 1.4.2 | 3 / 16 | |
| 1.4.0 | 3 / 16 | |
| 1.2.3 | 4 / 17 | |
| 1.2.0 | 4 / 17 | |
| 1.0.4 | 2 / 17 | |
| 1.0.3 | 2 / 17 | |
| 1.0.2 | 2 / 17 | |
| 1.0.0 | 2 / 17 |
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.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: kikobeats.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.