@wix/multilingual-manager
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Wix internal SDK package; missing repo/homepage and terse README are typical for this publisher's packages. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is declared as a runtime dependency; phantom-dep heuristic fires but lodash may be used indirectly via re-exports. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.11.0 | 2 / 13 | |
| 1.10.0 | 2 / 13 | |
| 1.9.0 | 2 / 13 | |
| 1.8.0 | 2 / 13 | |
| 1.7.0 | 2 / 13 | |
| 1.6.0 | 2 / 13 | |
| 1.5.0 | 2 / 13 | |
| 1.4.0 | 2 / 13 | |
| 1.3.0 | 2 / 13 | |
| 1.2.0 | 2 / 12 | |
| 1.1.0 | 2 / 12 | |
| 1.0.0 | 2 / 12 |
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.