@stream-io/video-react-sdk
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Stable pattern for this package; description omitted intentionally in sub-packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): SDK sub-package; sparse metadata is consistent across all versions of this package family. | ai | |
| dependencies | unvetted-dep:@stream-io/video-client | AI (dependencies): First-party sibling package from GetStream org; consistent across all versions. | ai | |
| dependencies | unvetted-dep:@stream-io/video-filters-web | AI (dependencies): First-party sibling package from GetStream org; consistent across all versions. | ai | |
| dependencies | unvetted-dep:@stream-io/video-react-bindings | AI (dependencies): First-party sibling package from GetStream org; consistent across all versions. | ai |
Versions (showing 32 of 232)
| Version | Deps | Published |
|---|---|---|
| 1.2.9 | 7 / 10 | |
| 1.2.8 | 7 / 10 | |
| 1.2.7 | 7 / 10 | |
| 1.2.6 | 7 / 10 | |
| 1.2.5 | 7 / 10 | |
| 1.2.4 | 7 / 10 | |
| 1.2.3 | 7 / 10 | |
| 1.2.2 | 7 / 10 | |
| 1.2.1 | 7 / 10 | |
| 1.2.0 | 7 / 10 | |
| 1.1.5 | 7 / 10 | |
| 1.1.4 | 7 / 10 | |
| 1.1.3 | 7 / 10 | |
| 1.1.2 | 7 / 10 | |
| 1.1.1 | 7 / 10 | |
| 1.1.0 | 7 / 10 | |
| 1.0.15 | 7 / 10 | |
| 1.0.14 | 7 / 10 | |
| 1.0.13 | 7 / 10 | |
| 1.0.12 | 7 / 10 | |
| 1.0.11 | 7 / 10 | |
| 1.0.10 | 7 / 10 | |
| 1.0.9 | 7 / 10 | |
| 1.0.8 | 7 / 10 | |
| 1.0.7 | 7 / 10 | |
| 1.0.6 | 7 / 10 | |
| 1.0.5 | 7 / 10 | |
| 1.0.4 | 7 / 10 | |
| 1.0.3 | 7 / 10 | |
| 1.0.2 | 7 / 10 | |
| 1.0.1 | 7 / 10 | |
| 1.0.0 | 7 / 10 |
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.