@docusaurus/logger
An encapsulated logger for semantically formatting console messages.
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.10.1 | 2 / 1 | |
| 3.10.0 | 2 / 1 | |
| 3.9.2 | 2 / 1 | |
| 3.9.1 | 2 / 1 | |
| 3.9.0 | 2 / 1 | |
| 3.8.1 | 2 / 1 | |
| 3.8.0 | 2 / 1 | |
| 3.7.0 | 2 / 1 | |
| 3.6.3 | 2 / 1 | |
| 3.6.2 | 2 / 1 | |
| 3.6.1 | 2 / 1 | |
| 3.6.0 | 2 / 1 | |
| 3.5.2 | 2 / 1 | |
| 3.5.1 | 2 / 1 | |
| 3.5.0 | 2 / 1 | |
| 3.4.0 | 2 / 1 | |
| 3.3.2 | 2 / 1 | |
| 3.3.0 | 2 / 1 | |
| 3.2.1 | 2 / 1 | |
| 3.2.0 | 2 / 1 | |
| 3.1.1 | 2 / 1 | |
| 3.1.0 | 2 / 1 | |
| 3.0.1 | 2 / 1 | |
| 3.0.0 | 2 / 1 | |
| 2.4.3 | 2 / 1 | |
| 2.4.2 | 2 / 1 | |
| 2.4.1 | 2 / 1 | |
| 2.4.0 | 2 / 1 | |
| 2.3.1 | 2 / 1 | |
| 2.3.0 | 2 / 1 | |
| 2.2.0 | 2 / 1 | |
| 2.1.0 | 2 / 1 | |
| 2.0.1 | 2 / 1 | |
| 2.0.0 | 2 / 1 |
v3.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.