@mongosh/i18n
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 2.22.0 | 1 / 5 | |
| 2.20.3 | 1 / 5 | |
| 2.20.2 | 1 / 5 | |
| 2.20.1 | 1 / 5 | |
| 2.20.0 | 1 / 6 | |
| 2.19.0 | 1 / 6 | |
| 2.17.0 | 1 / 6 | |
| 2.16.0 | 1 / 6 | |
| 2.15.4 | 1 / 6 | |
| 2.15.2 | 1 / 6 | |
| 2.15.0 | 1 / 6 | |
| 2.13.1 | 1 / 6 | |
| 2.13.0 | 1 / 6 | |
| 2.11.0 | 1 / 6 | |
| 2.9.1 | 1 / 6 | |
| 2.9.0 | 1 / 6 | |
| 2.8.0 | 1 / 6 | |
| 2.6.0 | 1 / 6 | |
| 2.4.0 | 1 / 6 | |
| 2.3.8 | 1 / 6 | |
| 2.3.7 | 1 / 6 | |
| 2.3.6 | 1 / 6 | |
| 2.3.5 | 1 / 6 | |
| 2.3.4 | 1 / 6 | |
| 2.3.3 | 1 / 6 | |
| 2.3.2 | 1 / 6 | |
| 2.3.1 | 1 / 6 | |
| 2.3.0 | 1 / 6 | |
| 2.2.15 | 1 / 6 | |
| 2.2.12 | 1 / 6 | |
| 2.2.11 | 1 / 6 | |
| 2.2.10 | 1 / 6 | |
| 2.2.9 | 1 / 6 | |
| 2.2.6 | 1 / 6 |
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
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.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.