@wix/headless-media
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Wix CI pipeline routinely publishes @wix/* packages at 0.0.0; not a malware indicator for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix CI mass-produces scoped internal packages with templated names and minimal metadata; pattern is stable across the @wix namespace. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with Wix internal SDK package publishing pattern; not a malware signal here. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.0.25 | 3 / 11 | |
| 0.0.24 | 3 / 11 | |
| 0.0.23 | 3 / 11 | |
| 0.0.22 | 3 / 11 | |
| 0.0.21 | 3 / 10 | |
| 0.0.20 | 3 / 10 | |
| 0.0.19 | 3 / 10 | |
| 0.0.18 | 3 / 10 | |
| 0.0.17 | 3 / 10 | |
| 0.0.16 | 3 / 10 | |
| 0.0.9 | 3 / 8 | |
| 0.0.8 | 3 / 8 | |
| 0.0.7 | 3 / 8 | |
| 0.0.6 | 3 / 8 | |
| 0.0.5 | 3 / 8 | |
| 0.0.4 | 3 / 8 | |
| 0.0.3 | 3 / 8 | |
| 0.0.2 | 2 / 8 | |
| 0.0.1 | 2 / 8 | |
| 0.0.0 | 3 / 10 |
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.