@tellescope/video-chat
Shared UI components designed with support for React and React Native in mind. To be used across Tellescope web apps and open-sourced modules.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo component; sparse README and missing keywords are stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across 810 versions; not a new risk for this package. | ai | |
| dependencies | unvetted-dep:amazon-chime-sdk-js | AI (dependencies): Expected core dependency for a video-chat component library built on Amazon Chime SDK. | ai | |
| dependencies | unvetted-dep:amazon-chime-sdk-component-library-react | AI (dependencies): Expected UI dependency for a Chime-based video-chat component library. | ai | |
| dependencies | unvetted-dep:@tellescope/react-components | AI (dependencies): Same-org sibling package; consistent with the @tellescope monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@tellescope/sdk | AI (phantom-deps): Same-org dep; phantom signal is a false positive for this monorepo structure. | ai | |
| phantom-deps | phantom-dep:@fontsource/roboto | AI (phantom-deps): Font dep declared in dependencies; org packaging pattern. | ai | |
| phantom-deps | phantom-dep:@mui/icons-material | AI (phantom-deps): UI dep declared in dependencies; org packaging pattern. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react | AI (phantom-deps): Dev tooling in dependencies; org packaging pattern. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): Dev tooling listed in dependencies instead of devDependencies; stable packaging pattern for this org. | ai | |
| phantom-deps | phantom-dep:@tellescope/utilities | AI (phantom-deps): Same-org dep; false positive for monorepo structure. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): Dev tooling in dependencies; org packaging pattern. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): Dev tooling in dependencies; org packaging pattern. | ai | |
| phantom-deps | phantom-dep:@tellescope/constants | AI (phantom-deps): Same-org dep; false positive for monorepo structure. | ai | |
| phantom-deps | phantom-dep:@mui/material | AI (phantom-deps): UI peer dep declared in dependencies; consistent across tellescope org packages. | ai | |
| phantom-deps | phantom-dep:styled-system | AI (phantom-deps): Styling dep declared in dependencies; org packaging pattern. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): MUI peer dep declared in dependencies; org packaging pattern. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): MUI peer dep declared in dependencies; org packaging pattern. | ai |
Versions (showing 100 of 266)
| Version | Deps | Published |
|---|---|---|
| 1.211.0 | 21 / 3 | |
| 1.210.0 | 21 / 3 | |
| 1.209.0 | 21 / 3 | |
| 1.208.0 | 21 / 3 | |
| 1.207.0 | 21 / 3 | |
| 1.206.0 | 21 / 3 | |
| 1.205.0 | 21 / 3 | |
| 1.204.2 | 21 / 3 | |
| 1.204.1 | 21 / 3 | |
| 1.204.0 | 21 / 3 | |
| 1.203.2 | 21 / 3 | |
| 1.203.1 | 21 / 3 | |
| 1.203.0 | 21 / 3 | |
| 1.202.0 | 21 / 3 | |
| 1.201.0 | 21 / 3 | |
| 1.200.2 | 21 / 3 | |
| 1.200.1 | 21 / 3 | |
| 1.200.0 | 21 / 3 | |
| 1.199.1 | 21 / 3 | |
| 1.199.0 | 21 / 3 | |
| 1.198.0 | 21 / 3 | |
| 1.197.0 | 21 / 3 | |
| 1.196.0 | 21 / 3 | |
| 1.195.0 | 21 / 3 | |
| 1.194.0 | 21 / 3 | |
| 1.193.0 | 21 / 3 | |
| 1.192.0 | 21 / 3 | |
| 1.191.0 | 21 / 3 | |
| 1.190.0 | 21 / 3 | |
| 1.189.0 | 21 / 3 | |
| 1.188.0 | 21 / 3 | |
| 1.187.0 | 21 / 3 | |
| 1.186.0 | 21 / 3 | |
| 1.185.2 | 21 / 3 | |
| 1.185.1 | 21 / 3 | |
| 1.185.0 | 21 / 3 | |
| 1.184.0 | 21 / 3 | |
| 1.183.0 | 21 / 3 | |
| 1.182.0 | 21 / 3 | |
| 1.181.1 | 21 / 3 | |
| 1.181.0 | 21 / 3 | |
| 1.180.0 | 21 / 3 | |
| 1.179.0 | 21 / 3 | |
| 1.178.0 | 21 / 3 | |
| 1.177.0 | 21 / 3 | |
| 1.176.0 | 21 / 3 | |
| 1.175.0 | 21 / 3 | |
| 1.174.0 | 21 / 3 | |
| 1.173.0 | 21 / 3 | |
| 1.172.1 | 21 / 3 | |
| 1.172.0 | 21 / 3 | |
| 1.171.1 | 21 / 3 | |
| 1.171.0 | 21 / 3 | |
| 1.170.0 | 21 / 3 | |
| 1.169.0 | 21 / 3 | |
| 1.168.0 | 21 / 3 | |
| 1.167.1 | 21 / 3 | |
| 1.167.0 | 21 / 3 | |
| 1.166.1 | 21 / 3 | |
| 1.166.0 | 21 / 3 | |
| 1.165.0 | 21 / 3 | |
| 1.164.0 | 21 / 3 | |
| 1.163.0 | 21 / 3 | |
| 1.162.0 | 21 / 3 | |
| 1.161.0 | 21 / 3 | |
| 1.160.1 | 21 / 3 | |
| 1.160.0 | 21 / 3 | |
| 1.159.0 | 21 / 3 | |
| 1.158.0 | 21 / 3 | |
| 1.157.1 | 21 / 3 | |
| 1.156.0 | 21 / 3 | |
| 1.155.0 | 21 / 3 | |
| 1.154.0 | 21 / 3 | |
| 1.153.1 | 21 / 3 | |
| 1.153.0 | 21 / 3 | |
| 1.152.0 | 21 / 3 | |
| 1.151.0 | 21 / 3 | |
| 1.150.1 | 21 / 3 | |
| 1.150.0 | 21 / 3 | |
| 1.149.0 | 21 / 3 | |
| 1.148.1 | 21 / 3 | |
| 1.148.0 | 21 / 3 | |
| 1.147.0 | 21 / 3 | |
| 1.146.0 | 21 / 3 | |
| 1.145.0 | 21 / 3 | |
| 1.144.0 | 21 / 3 | |
| 1.143.0 | 21 / 3 | |
| 1.142.0 | 21 / 3 | |
| 1.141.0 | 21 / 3 | |
| 1.140.0 | 21 / 3 | |
| 1.139.0 | 21 / 3 | |
| 1.138.0 | 21 / 3 | |
| 1.137.0 | 21 / 3 | |
| 1.136.1 | 21 / 3 | |
| 1.136.0 | 21 / 3 | |
| 1.135.0 | 21 / 3 | |
| 1.134.0 | 21 / 3 | |
| 1.133.1 | 21 / 3 | |
| 1.133.0 | 21 / 3 | |
| 1.132.0 | 21 / 3 |
v1.194.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.
v1.193.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.
v1.192.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.
v1.191.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.
v1.190.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.
v1.189.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.
v1.188.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.
v1.187.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.
v1.186.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.
v1.185.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.185.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.185.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.
v1.184.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.
v1.183.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.
v1.182.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.
v1.181.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.181.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.
v1.180.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.
v1.179.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.
v1.178.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.
v1.177.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.
v1.176.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.
v1.175.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.
v1.174.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.
v1.173.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.
v1.172.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.172.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.
v1.171.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.171.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.
v1.170.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.
v1.169.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.
v1.168.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.
v1.167.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.167.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.
v1.166.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.166.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.
v1.165.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.
v1.164.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.
v1.163.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.
v1.162.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.
v1.161.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.
v1.160.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.160.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.
v1.159.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.
v1.158.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.
v1.157.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.156.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.
v1.155.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.
v1.154.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.
v1.153.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.153.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.
v1.152.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.
v1.151.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.
v1.150.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.150.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.
v1.149.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.
v1.148.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.148.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.
v1.147.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.
v1.146.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.
v1.145.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.
v1.144.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.
v1.143.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.
v1.142.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.
v1.141.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.
v1.140.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.
v1.139.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.
v1.138.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.
v1.137.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.
v1.136.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.136.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.
v1.135.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.
v1.134.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.
v1.133.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.133.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.
v1.132.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.