@motech-development/node-logger
Logger for NodeJS applications
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 2 / 18 | |
| 1.4.0 | 2 / 30 | |
| 1.3.1 | 2 / 30 | |
| 1.3.0 | 2 / 29 | |
| 1.2.0 | 2 / 28 | |
| 1.1.14 | 2 / 27 | |
| 1.1.13 | 2 / 27 | |
| 1.1.12 | 2 / 27 | |
| 1.1.11 | 2 / 27 | |
| 1.1.10 | 2 / 27 | |
| 1.1.9 | 2 / 27 | |
| 1.1.8 | 2 / 27 | |
| 1.1.7 | 2 / 27 | |
| 1.1.6 | 2 / 27 | |
| 1.1.5 | 2 / 27 | |
| 1.1.4 | 2 / 27 | |
| 1.1.3 | 2 / 27 |
v1.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.