@ai-sdk/google
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 provenance confirms legitimate publish pipeline. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Vercel team membership changes are expected over time; vercel-release-bot remains the publisher with a strong track record. No malicious signals. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): jaredpalmer leaving Vercel's AI SDK maintainer list is a normal team change; vercel-release-bot continues publishing with consistent patterns. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by major version restructuring (v1.x to v2.x). Publisher is vercel-release-bot with strong track record; no other malicious signals. | ai |
Versions (showing 31 of 131)
| Version | Deps | Published |
|---|---|---|
| 2.0.53 | 2 / 6 | |
| 2.0.52 | 2 / 6 | |
| 2.0.51 | 2 / 6 | |
| 2.0.50 | 2 / 6 | |
| 2.0.49 | 2 / 6 | |
| 2.0.48 | 2 / 6 | |
| 2.0.47 | 2 / 6 | |
| 2.0.46 | 2 / 6 | |
| 2.0.45 | 2 / 6 | |
| 2.0.44 | 2 / 6 | |
| 2.0.43 | 2 / 6 | |
| 2.0.42 | 2 / 6 | |
| 2.0.41 | 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 / 6 | |
| 2.0.26 | 2 / 5 | |
| 2.0.25 | 2 / 5 | |
| 2.0.24 | 2 / 5 | |
| 1.1.0 | 2 / 5 |
v2.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v2.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.