@wix/services-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
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 internal rotation; publisher has strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with Wix internal team changes; no malicious indicators. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Wix CI publisher with established track record; dormancy likely reflects internal release cadence. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix internal CI publisher; missing metadata is a known pattern for Wix monorepo packages, not spam. | ai | |
| phantom-deps | phantom-dep:@wix/sdk-context | AI (phantom-deps): Same-org scope phantom dep; likely an indirect/type-only dependency, stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.7 | 3 / 11 | |
| 1.0.6 | 3 / 11 | |
| 1.0.5 | 3 / 11 | |
| 1.0.4 | 3 / 11 | |
| 1.0.3 | 3 / 11 | |
| 1.0.2 | 3 / 11 | |
| 1.0.1 | 3 / 11 | |
| 1.0.0 | 3 / 11 |
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
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.