@assistant-ui/react
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zustand | AI (phantom-deps): Re-exported via Radix UI dependencies; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-use-callback-ref | AI (phantom-deps): Direct dependency used in component exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-compose-refs | AI (phantom-deps): Direct dependency used in component exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-primitive | AI (phantom-deps): Direct dependency used in component exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-textarea-autosize | AI (phantom-deps): Direct dependency used in component exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-slot | AI (phantom-deps): Direct dependency used in component exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/primitive | AI (phantom-deps): Direct dependency used in component exports; stable pattern for this package. | ai | |
| provenance | regressed-provenance | AI (provenance): Manual publish by known maintainer yonom; publishConfig provenance:false is intentional for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): safe-content-frame is a first-party @assistant-ui-adjacent dep; benign additions expected across versions. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): JWT base64url decoding in auth code, not obfuscation. | ai | |
| provenance | slsa-provenance | AI (provenance): Package has SLSA provenance via Sigstore; strongest supply chain integrity signal, stable for this package going forward. | ai | |
| source-diff | large-new-source-files | AI (source-diff): UI component library for AI chat; adding new source files is expected growth. No large files (≥50KB) flagged, no script or dep changes — consistent with normal feature development. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-dropdown-menu | AI (dependencies): @radix-ui/react-dropdown-menu is a well-known, widely-trusted Radix UI component; entirely appropriate for a React UI component library. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD-published release with SLSA provenance is consistent with legitimate resumption of development, not account takeover. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from yonom to GitHub Actions CI/CD, consistent with intentional migration to automated publishing with SLSA provenance attestation. Not a suspicious actor. | ai | |
| phantom-deps | phantom-dep:@standard-schema/spec | AI (phantom-deps): @standard-schema/spec is a legitimate schema spec package used at config/type level; not being directly imported in source is expected for this kind of dependency. | ai | |
| dependencies | unvetted-dep:@assistant-ui/store | AI (dependencies): First-party scoped package from the assistant-ui org; expected internal dependency. | ai | |
| dependencies | unvetted-dep:@assistant-ui/core | AI (dependencies): First-party scoped package from the assistant-ui org; expected internal dependency. | ai | |
| dependencies | unvetted-dep:@assistant-ui/tap | AI (dependencies): First-party scoped package from the assistant-ui org; expected internal dependency. | ai | |
| dependencies | unvetted-dep:assistant-stream | AI (dependencies): First-party dependency from the assistant-ui ecosystem, same publisher and GitHub org. | ai | |
| dependencies | unvetted-dep:radix-ui | AI (dependencies): radix-ui is a well-known React UI primitives library; expected dependency for this UI component package. | ai | |
| dependencies | unvetted-dep:assistant-cloud | AI (dependencies): First-party dependency from the assistant-ui ecosystem, same publisher and GitHub org. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): nanoid is a well-known ID generation library; phantom-dep finding is benign for a build/config reference. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a well-known validation library; phantom-dep finding is benign for a build/config reference. | ai |
Versions (showing 27 of 429)
| Version | Deps | Published |
|---|---|---|
| 0.0.28 | 8 / 5 | |
| 0.0.27 | 8 / 5 | |
| 0.0.26 | 8 / 3 | |
| 0.0.25 | 8 / 3 | |
| 0.0.23 | 8 / 3 | |
| 0.0.22 | 8 / 3 | |
| 0.0.21 | 8 / 3 | |
| 0.0.20 | 9 / 2 | |
| 0.0.19 | 9 / 2 | |
| 0.0.18 | 9 / 2 | |
| 0.0.17 | 9 / 2 | |
| 0.0.16 | 8 / 2 | |
| 0.0.15 | 8 / 2 | |
| 0.0.14 | 8 / 2 | |
| 0.0.13 | 8 / 2 | |
| 0.0.12 | 8 / 2 | |
| 0.0.11 | 7 / 2 | |
| 0.0.10 | 7 / 2 | |
| 0.0.9 | 7 / 2 | |
| 0.0.8 | 7 / 2 | |
| 0.0.7 | 7 / 2 | |
| 0.0.6 | 7 / 2 | |
| 0.0.5 | 7 / 2 | |
| 0.0.4 | 7 / 3 | |
| 0.0.3 | 7 / 3 | |
| 0.0.2 | 7 / 3 | |
| 0.0.1 | 6 / 3 |
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.