@asteby/metacore-i18n
Metacore i18n — i18next factory, base ES/EN bundles, language switcher, RTL provider
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 1 / 10 | |
| 9.0.0 | 1 / 10 | |
| 8.0.0 | 1 / 10 | |
| 7.0.1 | 1 / 10 | |
| 7.0.0 | 1 / 10 | |
| 6.0.0 | 1 / 10 | |
| 5.1.0 | 1 / 10 | |
| 5.0.1 | 1 / 10 | |
| 5.0.0 | 1 / 10 | |
| 4.0.0 | 1 / 10 | |
| 3.0.0 | 1 / 10 | |
| 2.0.0 | 1 / 10 |
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
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.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.