@wix/autocms-collection-metadata-service
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Wix org team rotation via trusted CI publisher; not indicative of takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Wix org team rotation via trusted CI publisher; not indicative of takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Internal Wix package with infrequent updates; dormancy is expected for stable internal libs. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK packages consistently lack descriptions/repo URLs; this is a pipeline artifact, not a spam/malware signal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix autogenerated SDK packages intentionally omit descriptions; stable false positive for this package family. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.0.34 | 1 / 2 | |
| 1.0.33 | 1 / 2 | |
| 1.0.32 | 1 / 2 | |
| 1.0.31 | 1 / 2 | |
| 1.0.30 | 1 / 2 | |
| 1.0.29 | 1 / 2 | |
| 1.0.28 | 1 / 2 | |
| 1.0.27 | 1 / 2 | |
| 1.0.26 | 1 / 2 | |
| 1.0.25 | 1 / 2 | |
| 1.0.24 | 1 / 2 | |
| 1.0.23 | 1 / 2 | |
| 1.0.22 | 1 / 2 | |
| 1.0.21 | 1 / 2 | |
| 1.0.20 | 1 / 2 | |
| 1.0.19 | 1 / 1 | |
| 1.0.18 | 1 / 1 |
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.