@copilotkit/react-textarea
<img src="https://github.com/user-attachments/assets/0a6b64d9-e193-4940-a3f6-60334ac34084" alt="banner" style="border-radius: 12px; border: 2px solid #d6d4fa;" />
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): CopilotKit migrated publishing to GitHub Actions CI with SLSA attestation; this is the expected pattern for the org going forward. | ai | |
| source-diff | net-exec-file:dist/index.umd.js | AI (source-diff): UMD bundle for CDN delivery; sample shows standard UMD wrapper with no actual network fetch or eval. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:material-icons | AI (dependencies): material-icons is a well-known Google icon font package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive for this UI component package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-separator | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive for this UI component package. | ai | |
| phantom-deps | phantom-dep:material-icons | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive for this UI component package. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive for this UI component package. | ai |
Versions (showing 36 of 136)
| Version | Deps | Published |
|---|---|---|
| 1.4.4 | 22 / 17 | |
| 1.4.3 | 22 / 17 | |
| 1.4.2 | 22 / 17 | |
| 1.4.1 | 22 / 17 | |
| 1.4.0 | 22 / 17 | |
| 1.3.15 | 22 / 17 | |
| 1.3.14 | 22 / 17 | |
| 1.3.13 | 22 / 17 | |
| 1.3.12 | 22 / 17 | |
| 1.3.11 | 22 / 17 | |
| 1.3.10 | 22 / 17 | |
| 1.3.9 | 22 / 17 | |
| 1.3.8 | 22 / 17 | |
| 1.3.7 | 22 / 17 | |
| 1.3.6 | 22 / 17 | |
| 1.3.5 | 22 / 17 | |
| 1.3.4 | 22 / 17 | |
| 1.3.3 | 22 / 17 | |
| 1.3.2 | 22 / 17 | |
| 1.3.1 | 22 / 17 | |
| 1.3.0 | 22 / 23 | |
| 1.2.1 | 22 / 23 | |
| 1.2.0 | 22 / 23 | |
| 1.1.2 | 22 / 17 | |
| 1.1.1 | 22 / 17 | |
| 1.1.0 | 22 / 17 | |
| 1.0.9 | 22 / 17 | |
| 1.0.8 | 22 / 17 | |
| 1.0.7 | 22 / 17 | |
| 1.0.6 | 22 / 17 | |
| 1.0.5 | 22 / 17 | |
| 1.0.4 | 22 / 17 | |
| 1.0.3 | 23 / 17 | |
| 1.0.2 | 23 / 17 | |
| 1.0.1 | 23 / 17 | |
| 1.0.0 | 23 / 17 |
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
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.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.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.