@wix/monitoring-types
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 routine maintainer rotation via CI publisher; not indicative of takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org rotation context; removal paired with addition is expected for Wix internal packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Types-only internal package; long dormancy between releases is normal for stable type definitions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix internal CI-published package; missing metadata is a known pattern across their SDK packages, not a spam/malware signal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix internal packages consistently omit descriptions; stable false positive for this publisher. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 0 / 6 | |
| 0.17.0 | 0 / 6 | |
| 0.16.0 | 0 / 6 | |
| 0.15.0 | 0 / 6 | |
| 0.14.0 | 0 / 6 | |
| 0.13.0 | 0 / 6 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.