@whereby.com/browser-sdk
Modules for integration Whereby video in web apps
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:heresy | AI (dependencies): heresy is a known custom-elements polyfill; legitimate use in a browser SDK. | ai | |
| source-diff | encoded-string-file:dist/cdn/v3-react.js | AI (source-diff): Long strings are GLSL shader source embedded in WebGL bundle for background effects — not obfuscated payloads. | ai | |
| phantom-deps | phantom-dep:@whereby.com/media | AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): clsx is a declared runtime dep; phantom-dep false positive for this package. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 3.20.19 | 6 / 30 | |
| 3.20.18 | 6 / 30 | |
| 3.20.17 | 6 / 30 | |
| 3.20.16 | 6 / 30 | |
| 3.20.15 | 6 / 30 | |
| 3.20.14 | 6 / 30 | |
| 3.20.13 | 6 / 30 | |
| 3.20.12 | 6 / 30 | |
| 3.20.11 | 6 / 30 | |
| 3.20.10 | 6 / 30 | |
| 3.20.9 | 6 / 30 | |
| 3.20.8 | 6 / 30 | |
| 3.20.7 | 6 / 30 | |
| 3.20.6 | 6 / 30 | |
| 3.19.15 | 6 / 30 | |
| 3.19.14 | 6 / 30 | |
| 3.19.12 | 6 / 30 | |
| 3.19.11 | 6 / 30 | |
| 3.19.9 | 6 / 30 | |
| 3.19.8 | 6 / 30 | |
| 3.19.7 | 6 / 30 | |
| 3.18.34 | 6 / 30 | |
| 3.18.29 | 6 / 30 | |
| 3.18.28 | 6 / 30 | |
| 3.18.26 | 6 / 30 | |
| 3.18.18 | 6 / 30 | |
| 3.18.15 | 6 / 30 | |
| 3.18.13 | 6 / 30 | |
| 3.18.12 | 6 / 30 | |
| 3.18.10 | 6 / 30 | |
| 3.18.9 | 6 / 30 | |
| 3.18.7 | 6 / 30 | |
| 3.18.4 | 6 / 30 | |
| 3.15.0 | 6 / 30 | |
| 3.14.9 | 6 / 29 | |
| 3.14.4 | 6 / 29 | |
| 3.14.3 | 6 / 29 | |
| 3.13.11 | 6 / 29 | |
| 3.13.9 | 6 / 29 | |
| 3.13.8 | 6 / 29 | |
| 3.13.7 | 6 / 29 | |
| 3.13.5 | 6 / 29 | |
| 3.13.2 | 6 / 29 | |
| 3.12.23 | 8 / 29 | |
| 3.12.21 | 8 / 29 | |
| 3.12.15 | 7 / 21 | |
| 3.12.11 | 7 / 21 |
v3.20.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.