← Home

@copilotkit/react-textarea

npm Repository Homepage

<img src="https://github.com/user-attachments/assets/0a6b64d9-e193-4940-a3f6-60334ac34084" alt="banner" style="border-radius: 12px; border: 2px solid #d6d4fa;" />

100
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

copilotkit

Keywords

aiassistantautomationcopilotcopilotkitjavascriptnextjsnodejsreacttextarea

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 of 136)

Version Deps Published
1.63.2 21 / 16
1.63.1 21 / 16
1.63.0 21 / 16
1.62.3 21 / 16
1.62.2 21 / 16
1.62.1 21 / 16
1.62.0 21 / 16
1.61.2 21 / 16
1.61.1 21 / 16
1.60.2 21 / 16
1.60.1 21 / 16
1.60.0 21 / 16
1.59.5 21 / 16
1.59.4 21 / 16
1.59.3 21 / 16
1.59.2 21 / 16
1.59.1 21 / 16
1.59.0 21 / 16
1.58.0 21 / 16
1.57.4 21 / 16
1.57.3 21 / 16
1.57.2 21 / 16
1.57.1 21 / 16
1.57.0 21 / 16
1.56.5 21 / 16
1.56.4 21 / 16
1.56.3 21 / 16
1.56.2 21 / 16
1.56.1 21 / 16
1.56.0 21 / 16
1.55.3 21 / 16
1.55.2 21 / 16
1.55.1 21 / 16
1.55.0 21 / 16
1.54.1 21 / 17
1.54.0 21 / 17
1.53.0 21 / 17
1.52.1 21 / 17
1.52.0 21 / 17
1.51.4 21 / 19
1.51.3 21 / 18
1.51.2 21 / 18
1.51.1 18 / 21
1.51.0 18 / 21
1.50.1 21 / 18
1.50.0 21 / 18
1.10.6 21 / 18
1.10.5 21 / 18
1.10.4 21 / 18
1.10.3 21 / 18
1.10.2 21 / 18
1.10.1 21 / 18
1.10.0 21 / 18
1.9.3 21 / 18
1.9.2 21 / 18
1.9.1 21 / 18
1.9.0 21 / 18
1.8.14 22 / 17
1.8.13 22 / 17
1.8.12 22 / 17
1.8.11 22 / 17
1.8.10 22 / 17
1.8.9 22 / 17
1.8.8 22 / 17
1.8.7 22 / 17
1.8.6 22 / 17
1.8.5 22 / 17
1.8.4 22 / 17
1.8.3 22 / 17
1.8.2 22 / 17
1.8.1 22 / 17
1.8.0 22 / 17
1.7.1 22 / 17
1.7.0 22 / 17
1.6.0 22 / 17
1.5.20 22 / 17
1.5.19 22 / 17
1.5.18 22 / 17
1.5.17 22 / 17
1.5.16 22 / 17
1.5.15 22 / 17
1.5.14 22 / 17
1.5.13 22 / 17
1.5.12 22 / 17
1.5.11 22 / 17
1.5.10 22 / 17
1.5.9 22 / 17
1.5.8 22 / 17
1.5.7 22 / 17
1.5.6 22 / 17
1.5.5 22 / 17
1.5.4 22 / 17
1.5.3 22 / 17
1.5.2 22 / 17
1.5.1 22 / 17
1.5.0 22 / 17
1.4.8 22 / 17
1.4.7 22 / 17
1.4.6 22 / 17
1.4.5 22 / 17
Showing 100 of 136 Next page →

v1.63.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.63.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.63.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.62.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.62.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.62.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.62.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.61.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.8.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.