← Home

@ai-sdk/react

100
Versions
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

vercel-release-botmatheussmatt.straka

Keywords

aireact

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Vercel migrated from vercel-release-bot to GitHub Actions CI; SLSA attestation confirms legitimacy. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers matheuss and matt.straka are Vercel employees; this is a documented internal transition. Publisher remains vercel-release-bot. ai
maintainer-change maintainer-removed AI (maintainer-change): jaredpalmer's removal reflects a known Vercel org transition; not indicative of takeover given vercel-release-bot remains the publisher. ai
publish-pattern dormant-publish AI (publish-pattern): Apparent dormancy is an artifact of the large version gap (v1.1.8 to v3.0.141) between last approved and current. Package has 850 versions and 5.2M weekly downloads — continuously active. ai
publish-pattern new-deps-added AI (publish-pattern): New dep 'ai' is the core Vercel AI SDK package replacing @ai-sdk/ui-utils; a legitimate architectural consolidation within the same trusted org. ai
provenance no-provenance AI (provenance): vercel-release-bot is a well-established publisher with 4383 approved packages; lack of Sigstore provenance is not a meaningful risk signal for this publisher. ai

Versions (showing 100 of 332)

Version Deps Published
3.0.6 4 / 16
3.0.5 4 / 16
3.0.4 4 / 16
3.0.3 4 / 16
3.0.2 4 / 16
3.0.1 4 / 16
3.0.0 4 / 16
2.0.206 4 / 13
2.0.205 4 / 13
2.0.204 4 / 13
2.0.203 4 / 13
2.0.202 4 / 13
2.0.201 4 / 13
2.0.200 4 / 13
2.0.199 4 / 13
2.0.198 4 / 13
2.0.197 4 / 13
2.0.196 4 / 13
2.0.195 4 / 13
2.0.194 4 / 13
2.0.192 4 / 13
2.0.190 4 / 13
2.0.189 4 / 13
2.0.188 4 / 13
2.0.187 4 / 13
2.0.186 4 / 13
2.0.185 4 / 13
2.0.184 4 / 13
2.0.183 4 / 13
2.0.182 4 / 13
2.0.181 4 / 13
2.0.180 4 / 13
2.0.178 4 / 13
2.0.177 4 / 13
2.0.176 4 / 13
2.0.175 4 / 13
2.0.174 4 / 13
2.0.173 4 / 13
2.0.172 4 / 13
2.0.171 4 / 13
2.0.170 4 / 13
2.0.169 4 / 13
2.0.168 4 / 13
2.0.167 4 / 13
2.0.166 4 / 13
2.0.165 4 / 13
2.0.164 4 / 13
2.0.163 4 / 13
2.0.162 4 / 13
2.0.161 4 / 13
2.0.160 4 / 13
2.0.159 4 / 15
2.0.158 4 / 15
2.0.157 4 / 15
2.0.156 4 / 15
2.0.155 4 / 15
2.0.154 4 / 15
2.0.153 4 / 15
2.0.152 4 / 15
2.0.151 4 / 15
2.0.150 4 / 15
2.0.149 4 / 15
2.0.148 4 / 15
2.0.147 4 / 15
2.0.146 4 / 15
2.0.145 4 / 15
2.0.144 4 / 15
2.0.143 4 / 15
2.0.142 4 / 15
2.0.141 4 / 15
2.0.140 4 / 15
2.0.139 4 / 15
2.0.138 4 / 15
2.0.137 4 / 15
2.0.136 4 / 15
2.0.135 4 / 15
2.0.134 4 / 15
2.0.133 4 / 15
2.0.132 4 / 15
2.0.131 4 / 15
2.0.130 4 / 15
2.0.129 4 / 15
2.0.128 4 / 15
2.0.127 4 / 15
2.0.126 4 / 15
2.0.125 4 / 15
2.0.124 4 / 15
2.0.123 4 / 15
2.0.122 4 / 15
2.0.121 4 / 15
2.0.120 4 / 15
2.0.119 4 / 15
2.0.118 4 / 15
2.0.117 4 / 15
2.0.116 4 / 15
2.0.115 4 / 15
2.0.114 4 / 15
2.0.113 4 / 15
2.0.112 4 / 15
2.0.111 4 / 15
Showing 100 of 332 Next page →

v2.0.206

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.

v2.0.205

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.

v2.0.204

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.

v2.0.203

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.

v2.0.202

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.

v2.0.201

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.

v2.0.200

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.

v2.0.199

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.

v2.0.198

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.

v2.0.197

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.

v2.0.196

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.

v2.0.195

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.

v2.0.194

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.

v2.0.192

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.

v2.0.190

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.

v2.0.188

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.

v2.0.187

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.

v2.0.186

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.

v2.0.185

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.

v2.0.184

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.

v2.0.183

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.

v2.0.150

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.139

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.138

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.137

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.136

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.135

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.123

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.121

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.