@ai-sdk/amazon-bedrock
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are part of Vercel's AI SDK team; package is published by vercel-release-bot with strong track record. Team changes are expected for an active Vercel project. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of jaredpalmer reflects normal Vercel team evolution; vercel-release-bot remains the publisher with consistent approval history. | ai | |
| provenance | no-provenance | AI (provenance): vercel-release-bot is a well-established trusted publisher; absence of Sigstore provenance is a minor gap, not a risk signal for this package. | ai | |
| dependencies | unvetted-dep:aws4fetch | AI (dependencies): aws4fetch is a legitimate, widely-used AWS Signature V4 signing library for fetch-based/edge environments. Its use here is architecturally appropriate as a replacement for @aws-sdk/client-bedrock-runtime. | ai |
Versions (showing 58 of 164)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 6 / 6 | |
| 4.0.1 | 6 / 6 | |
| 4.0.0 | 6 / 6 | |
| 3.0.103 | 6 / 6 | |
| 3.0.102 | 6 / 6 | |
| 3.0.101 | 6 / 6 | |
| 3.0.100 | 6 / 6 | |
| 3.0.99 | 6 / 6 | |
| 3.0.97 | 6 / 6 | |
| 3.0.96 | 6 / 6 | |
| 3.0.95 | 6 / 6 | |
| 3.0.94 | 6 / 6 | |
| 3.0.93 | 6 / 6 | |
| 3.0.92 | 6 / 6 | |
| 3.0.91 | 6 / 6 | |
| 3.0.90 | 6 / 6 | |
| 3.0.89 | 6 / 6 | |
| 3.0.88 | 6 / 6 | |
| 3.0.87 | 6 / 6 | |
| 3.0.86 | 6 / 6 | |
| 3.0.85 | 6 / 6 | |
| 3.0.84 | 6 / 6 | |
| 3.0.83 | 6 / 6 | |
| 3.0.82 | 6 / 6 | |
| 3.0.81 | 6 / 6 | |
| 3.0.80 | 6 / 6 | |
| 3.0.79 | 6 / 6 | |
| 3.0.78 | 6 / 6 | |
| 3.0.77 | 6 / 6 | |
| 3.0.76 | 6 / 6 | |
| 3.0.75 | 6 / 6 | |
| 3.0.74 | 6 / 6 | |
| 3.0.73 | 6 / 6 | |
| 3.0.72 | 6 / 6 | |
| 3.0.71 | 6 / 6 | |
| 3.0.70 | 6 / 6 | |
| 3.0.69 | 6 / 6 | |
| 3.0.68 | 6 / 6 | |
| 3.0.67 | 6 / 6 | |
| 3.0.66 | 6 / 6 | |
| 3.0.65 | 6 / 6 | |
| 3.0.64 | 6 / 6 | |
| 3.0.63 | 6 / 6 | |
| 3.0.62 | 6 / 6 | |
| 3.0.61 | 6 / 6 | |
| 3.0.60 | 6 / 6 | |
| 3.0.59 | 6 / 6 | |
| 3.0.57 | 6 / 6 | |
| 3.0.56 | 6 / 6 | |
| 3.0.55 | 6 / 6 | |
| 3.0.54 | 6 / 6 | |
| 3.0.53 | 6 / 6 | |
| 3.0.52 | 6 / 6 | |
| 3.0.51 | 6 / 6 | |
| 3.0.50 | 6 / 5 | |
| 3.0.49 | 6 / 5 | |
| 3.0.48 | 6 / 5 | |
| 1.1.6 | 3 / 7 |
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.103
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.102
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.101
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.100
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.99
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.