@veritone/chat-ui
A React component library for building chat interfaces that interact with `veri-agents-api` APIs via the `@veritone/agent-sdk`.
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across all 16 versions; internal tooling package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all versions; common for internal org packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Veritone UI library; sparse metadata is expected for org-scoped packages, not a spam/malware indicator. | ai | |
| phantom-deps | phantom-dep:@react-spring/web | AI (phantom-deps): @react-spring/web is a declared runtime dep; phantom-dep heuristic fires as false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.1.13 | 1 / 18 | |
| 0.1.12 | 1 / 18 | |
| 0.1.11 | 1 / 18 | |
| 0.1.9 | 1 / 18 | |
| 0.1.8 | 2 / 18 | |
| 0.1.7 | 2 / 18 | |
| 0.1.6 | 2 / 18 | |
| 0.1.5 | 2 / 10 | |
| 0.1.4 | 3 / 10 | |
| 0.1.3 | 3 / 10 | |
| 0.1.2 | 3 / 10 | |
| 0.1.1 | 3 / 10 |
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.