@wix/monitoring-browser-panorama
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@wix/monitoring-common-sentry | AI (dependencies): Wix-namespaced sibling monitoring package; consistent with this package's purpose and publisher track record. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wix package; missing public metadata is expected for proprietary corporate tooling. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal package; absent description is consistent across Wix internal packages. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher pattern; provenance not configured for this org's packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 2 / 20 | |
| 0.11.0 | 2 / 20 | |
| 0.10.0 | 2 / 20 | |
| 0.9.0 | 2 / 20 | |
| 0.8.0 | 2 / 20 | |
| 0.7.0 | 2 / 20 | |
| 0.6.0 | 2 / 20 | |
| 0.5.0 | 2 / 20 | |
| 0.4.0 | 2 / 20 |
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.