@wix/metro-public-utils
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
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): Internal Wix utility package; missing metadata is expected for private monorepo packages, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal package; missing description is consistent across Wix internal packages. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher pattern; no provenance is consistent across this publisher's packages. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.0.51 | 1 / 7 | |
| 1.0.50 | 1 / 5 | |
| 1.0.49 | 1 / 5 | |
| 1.0.48 | 1 / 5 | |
| 1.0.47 | 1 / 5 | |
| 1.0.46 | 1 / 5 | |
| 1.0.45 | 1 / 5 | |
| 1.0.44 | 1 / 5 | |
| 1.0.43 | 1 / 5 | |
| 1.0.42 | 1 / 5 | |
| 1.0.41 | 1 / 5 |
v1.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.