winston-loki
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with verified author identity, clean version diff, no install scripts, and publisher has a clean track record. Dormancy alone is insufficient to reject. | ai | |
| dependencies | unvetted-dep:btoa | AI (dependencies): btoa is a standard base64 encoding polyfill; appropriate dependency for a Loki transport that encodes log payloads. | ai | |
| dependencies | unvetted-dep:snappy | AI (dependencies): snappy is an optional dependency for Snappy compression support; well-known native binding with legitimate use in this transport. | ai | |
| dependencies | unvetted-dep:protobufjs | AI (dependencies): protobufjs is a well-known protobuf implementation; appropriate for a Loki transport that uses protobuf wire format. | ai | |
| dependencies | unvetted-dep:url-polyfill | AI (dependencies): url-polyfill is a standard URL API polyfill; appropriate for cross-environment compatibility in a transport package. | ai | |
| dependencies | unvetted-dep:async-exit-hook | AI (dependencies): async-exit-hook is a utility for async cleanup on process exit; appropriate for a transport that needs to flush logs before shutdown. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 6.1.4 | 6 / 12 | |
| 6.1.2 | 5 / 12 | |
| 6.1.0 | 5 / 12 | |
| 6.0.8 | 6 / 12 | |
| 6.0.7 | 6 / 12 | |
| 6.0.5 | 5 / 12 | |
| 6.0.4 | 5 / 12 | |
| 6.0.3 | 5 / 12 | |
| 6.0.2 | 5 / 12 | |
| 6.0.1 | 5 / 12 | |
| 6.0.0 | 5 / 12 | |
| 5.1.2 | 6 / 12 | |
| 5.1.1 | 6 / 12 | |
| 5.1.0 | 6 / 12 | |
| 5.0.0 | 6 / 12 |
v6.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.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: janianttonen.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.