@wix/monitoring
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 internal team rotation via trusted wix-ci-publisher; stable pattern for this org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Wix internal team rotation; removal paired with addition is expected for this org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix internal SDK package; sparse metadata is a monorepo convention, not a spam/malware signal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix SDK packages consistently omit descriptions; stable false positive for this publisher. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 1 / 12 | |
| 1.0.0 | 1 / 12 | |
| 0.27.0 | 1 / 12 | |
| 0.26.0 | 1 / 12 | |
| 0.25.0 | 1 / 12 | |
| 0.24.0 | 1 / 12 | |
| 0.23.0 | 1 / 12 | |
| 0.22.0 | 1 / 12 |
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.