@ai-sdk/groq
The **[Groq provider](https://ai-sdk.dev/providers/ai-sdk-providers/groq)** for the [AI SDK](https://ai-sdk.dev/docs) contains language model support for the Groq chat and completion APIs, transcription support, and browser search tool.
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): Migration from vercel-release-bot to GitHub Actions CI; SLSA attestation confirms legitimate pipeline change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (matheuss, matt.straka) are Vercel engineers; change is consistent with normal team evolution at Vercel, not a hostile takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): jaredpalmer's removal is consistent with Vercel team restructuring; published by vercel-release-bot with strong track record. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump (v1→v3) after dormancy reflects SDK restructuring, not account takeover. Publisher is vercel-release-bot with 4389 approved packages. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): @ai-sdk/groq is a legitimate Vercel AI SDK scoped package for Groq integration; Levenshtein match to 'glob' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @ai-sdk/groq is a legitimate Vercel AI SDK scoped package for Groq integration; Levenshtein match to 'got' is a false positive with no impersonation intent. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 3.0.39 | 2 / 6 | |
| 3.0.38 | 2 / 6 | |
| 3.0.37 | 2 / 6 | |
| 3.0.36 | 2 / 6 | |
| 3.0.35 | 2 / 6 | |
| 3.0.34 | 2 / 6 | |
| 3.0.33 | 2 / 6 | |
| 3.0.32 | 2 / 6 | |
| 3.0.31 | 2 / 6 | |
| 3.0.30 | 2 / 6 | |
| 3.0.29 | 2 / 6 | |
| 3.0.28 | 2 / 6 | |
| 3.0.27 | 2 / 6 | |
| 3.0.26 | 2 / 6 | |
| 3.0.25 | 2 / 6 | |
| 3.0.24 | 2 / 6 | |
| 3.0.23 | 2 / 6 | |
| 3.0.22 | 2 / 6 | |
| 3.0.21 | 2 / 6 | |
| 3.0.20 | 2 / 6 | |
| 3.0.19 | 2 / 6 | |
| 3.0.18 | 2 / 6 | |
| 3.0.17 | 2 / 6 | |
| 3.0.16 | 2 / 6 | |
| 3.0.15 | 2 / 6 | |
| 3.0.14 | 2 / 6 | |
| 3.0.13 | 2 / 6 | |
| 3.0.12 | 2 / 6 | |
| 3.0.11 | 2 / 6 | |
| 3.0.10 | 2 / 6 | |
| 3.0.9 | 2 / 6 | |
| 3.0.8 | 2 / 6 | |
| 3.0.7 | 2 / 6 | |
| 3.0.6 | 2 / 6 | |
| 3.0.5 | 2 / 6 | |
| 3.0.4 | 2 / 6 | |
| 3.0.3 | 2 / 6 | |
| 3.0.2 | 2 / 6 | |
| 3.0.1 | 2 / 6 | |
| 3.0.0 | 2 / 6 | |
| 2.0.40 | 2 / 6 | |
| 2.0.39 | 2 / 6 | |
| 2.0.38 | 2 / 6 | |
| 2.0.37 | 2 / 6 | |
| 2.0.36 | 2 / 6 | |
| 2.0.35 | 2 / 6 | |
| 2.0.34 | 2 / 6 | |
| 2.0.33 | 2 / 6 | |
| 2.0.32 | 2 / 6 | |
| 2.0.31 | 2 / 6 | |
| 2.0.30 | 2 / 6 | |
| 2.0.29 | 2 / 6 | |
| 2.0.28 | 2 / 6 | |
| 2.0.27 | 2 / 5 | |
| 2.0.26 | 2 / 5 | |
| 2.0.25 | 2 / 5 | |
| 1.1.7 | 2 / 5 |
v3.0.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.36
2 findingsThis version was published by a different npm account than previous versions on 2026-04-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.39
2 findingsThis version was published by a different npm account than previous versions on 2026-04-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.