ai-sdk-provider-claude-code
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.4.4 | 3 / 14 | |
| 3.4.3 | 3 / 14 | |
| 3.4.2 | 3 / 14 | |
| 3.4.1 | 3 / 14 | |
| 3.4.0 | 3 / 14 | |
| 3.3.6 | 3 / 14 | |
| 3.3.5 | 3 / 14 | |
| 3.3.4 | 3 / 14 | |
| 3.3.3 | 3 / 14 | |
| 3.3.2 | 3 / 14 | |
| 3.3.1 | 3 / 14 | |
| 3.3.0 | 3 / 14 | |
| 3.2.1 | 3 / 14 | |
| 3.1.0 | 3 / 14 | |
| 3.0.1 | 3 / 14 | |
| 3.0.0 | 3 / 14 | |
| 2.3.0 | 3 / 14 | |
| 2.2.4 | 3 / 14 | |
| 2.2.3 | 3 / 14 | |
| 2.2.2 | 3 / 14 | |
| 2.2.1 | 3 / 14 | |
| 2.2.0 | 3 / 14 |
v3.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.