evlog
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from hugo_rcd to GitHub Actions as part of a legitimate transition to automated CI/CD publishing; SLSA provenance attestation confirms the same repo/author identity. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): defu is a well-established UnJS/Nuxt ecosystem utility; its addition is consistent with evlog's Nuxt/Nitro focus and poses no supply chain risk. | ai | |
| provenance | no-provenance | AI (provenance): Package is a legitimate Nuxt/Nitro logging library; lack of Sigstore provenance is a best-practice gap, not a security risk for this package. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 2.18.1 | 0 / 41 | |
| 2.17.0 | 0 / 30 | |
| 2.14.1 | 0 / 28 | |
| 2.14.0 | 0 / 28 | |
| 2.13.0 | 0 / 28 | |
| 2.12.0 | 0 / 28 | |
| 2.11.1 | 0 / 28 | |
| 2.11.0 | 0 / 28 | |
| 2.10.0 | 0 / 27 | |
| 2.9.0 | 0 / 27 | |
| 2.8.0 | 0 / 26 | |
| 2.7.0 | 0 / 22 | |
| 2.6.0 | 0 / 20 | |
| 2.5.0 | 0 / 20 | |
| 2.4.1 | 0 / 20 | |
| 2.4.0 | 0 / 20 | |
| 2.3.0 | 0 / 18 | |
| 2.1.0 | 0 / 13 | |
| 2.0.0 | 0 / 13 | |
| 1.11.0 | 0 / 13 | |
| 1.10.0 | 0 / 13 | |
| 1.9.0 | 0 / 13 | |
| 1.8.0 | 0 / 13 | |
| 1.7.0 | 0 / 9 | |
| 1.6.0 | 0 / 9 | |
| 1.5.0 | 2 / 9 | |
| 1.4.0 | 2 / 9 | |
| 1.3.0 | 2 / 9 | |
| 1.2.0 | 2 / 9 | |
| 1.1.0 | 1 / 9 | |
| 1.0.1 | 1 / 9 | |
| 1.0.0 | 1 / 9 | |
| 0.1.0 | 1 / 9 |
v2.18.1
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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.17.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-09. This could indicate a legitimate maintainer transition or an account compromise.
v2.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.