@emartech/json-logger
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 9.2.5 | 1 / 23 | |
| 9.2.4 | 1 / 23 | |
| 9.2.3 | 1 / 23 | |
| 9.2.2 | 1 / 22 | |
| 9.2.1 | 1 / 25 | |
| 9.2.0 | 1 / 25 | |
| 9.1.0 | 1 / 25 | |
| 9.0.1 | 1 / 24 | |
| 9.0.0 | 1 / 23 |
v9.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.