@kong-ui-public/i18n
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.5.0 | 3 / 0 | |
| 2.4.6 | 3 / 0 | |
| 2.4.5 | 3 / 0 | |
| 2.4.4 | 3 / 0 | |
| 2.4.3 | 3 / 0 | |
| 2.4.2 | 3 / 0 | |
| 2.4.1 | 3 / 0 | |
| 2.4.0 | 3 / 0 | |
| 2.3.2 | 3 / 0 | |
| 2.3.1 | 3 / 0 | |
| 2.3.0 | 3 / 0 | |
| 2.2.10 | 3 / 0 | |
| 2.2.9 | 3 / 0 | |
| 2.2.8 | 3 / 0 | |
| 2.2.7 | 3 / 0 | |
| 2.2.6 | 3 / 0 | |
| 2.2.5 | 3 / 0 | |
| 2.2.4 | 3 / 0 | |
| 2.2.3 | 3 / 0 | |
| 2.2.2 | 3 / 0 | |
| 2.2.1 | 3 / 0 | |
| 2.2.0 | 3 / 0 | |
| 2.1.6 | 3 / 0 |
v2.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.