@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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.d.mts | AI (source-diff): Long lines are TypeScript union types for model IDs, not obfuscation; stable for this package. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo CI publishes multiple packages in quick succession; expected pattern. | ai | |
| 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 100 of 241)
| Version | Deps | Published |
|---|---|---|
| 5.0.34 | 7 / 6 | |
| 5.0.33 | 7 / 6 | |
| 5.0.32 | 7 / 6 | |
| 5.0.31 | 7 / 6 | |
| 5.0.30 | 7 / 6 | |
| 5.0.29 | 7 / 6 | |
| 5.0.28 | 7 / 6 | |
| 5.0.27 | 7 / 6 | |
| 5.0.26 | 7 / 6 | |
| 5.0.25 | 7 / 6 | |
| 5.0.24 | 7 / 6 | |
| 5.0.23 | 7 / 6 | |
| 5.0.22 | 7 / 6 | |
| 5.0.21 | 7 / 6 | |
| 5.0.20 | 7 / 6 | |
| 5.0.19 | 7 / 6 | |
| 5.0.17 | 7 / 6 | |
| 5.0.16 | 7 / 6 | |
| 5.0.15 | 7 / 6 | |
| 5.0.14 | 7 / 6 | |
| 5.0.13 | 7 / 6 | |
| 5.0.12 | 7 / 6 | |
| 5.0.11 | 7 / 6 | |
| 5.0.10 | 7 / 6 | |
| 5.0.9 | 7 / 6 | |
| 5.0.8 | 7 / 6 | |
| 5.0.7 | 7 / 6 | |
| 5.0.6 | 7 / 6 | |
| 5.0.5 | 7 / 6 | |
| 5.0.4 | 7 / 6 | |
| 5.0.3 | 7 / 6 | |
| 5.0.2 | 7 / 6 | |
| 5.0.1 | 7 / 6 | |
| 5.0.0 | 7 / 6 | |
| 4.0.143 | 7 / 6 | |
| 4.0.142 | 7 / 6 | |
| 4.0.141 | 7 / 6 | |
| 4.0.140 | 7 / 6 | |
| 4.0.139 | 7 / 6 | |
| 4.0.138 | 7 / 6 | |
| 4.0.137 | 7 / 6 | |
| 4.0.136 | 7 / 6 | |
| 4.0.135 | 7 / 6 | |
| 4.0.134 | 7 / 6 | |
| 4.0.133 | 7 / 6 | |
| 4.0.132 | 7 / 6 | |
| 4.0.131 | 7 / 6 | |
| 4.0.130 | 7 / 6 | |
| 4.0.129 | 7 / 6 | |
| 4.0.128 | 7 / 6 | |
| 4.0.127 | 7 / 6 | |
| 4.0.126 | 7 / 6 | |
| 4.0.125 | 7 / 6 | |
| 4.0.124 | 7 / 6 | |
| 4.0.123 | 7 / 6 | |
| 4.0.122 | 7 / 6 | |
| 4.0.121 | 7 / 6 | |
| 4.0.120 | 7 / 6 | |
| 4.0.119 | 7 / 6 | |
| 4.0.118 | 7 / 6 | |
| 4.0.117 | 7 / 6 | |
| 4.0.116 | 7 / 6 | |
| 4.0.115 | 7 / 6 | |
| 4.0.114 | 7 / 6 | |
| 4.0.113 | 7 / 6 | |
| 4.0.112 | 7 / 6 | |
| 4.0.111 | 6 / 6 | |
| 4.0.110 | 6 / 6 | |
| 4.0.109 | 6 / 6 | |
| 4.0.108 | 6 / 6 | |
| 4.0.107 | 6 / 6 | |
| 4.0.106 | 6 / 6 | |
| 4.0.105 | 6 / 6 | |
| 4.0.104 | 6 / 6 | |
| 4.0.103 | 6 / 6 | |
| 4.0.101 | 6 / 6 | |
| 4.0.100 | 6 / 6 | |
| 4.0.99 | 6 / 6 | |
| 4.0.98 | 6 / 6 | |
| 4.0.97 | 6 / 6 | |
| 4.0.96 | 6 / 6 | |
| 4.0.95 | 6 / 6 | |
| 4.0.94 | 6 / 6 | |
| 4.0.93 | 6 / 6 | |
| 4.0.92 | 6 / 6 | |
| 4.0.91 | 6 / 6 | |
| 4.0.90 | 6 / 6 | |
| 4.0.89 | 6 / 6 | |
| 4.0.88 | 6 / 6 | |
| 4.0.87 | 6 / 6 | |
| 4.0.86 | 6 / 6 | |
| 4.0.85 | 6 / 6 | |
| 4.0.84 | 6 / 6 | |
| 4.0.83 | 6 / 6 | |
| 4.0.82 | 6 / 6 | |
| 4.0.81 | 6 / 6 | |
| 4.0.80 | 6 / 6 | |
| 4.0.79 | 6 / 6 | |
| 4.0.78 | 6 / 6 | |
| 4.0.77 | 6 / 6 |
v5.0.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.143
1 findingPublished via CI/CD with a Sigstore attestation that VERIFIED against the pinned Sigstore trust root (predicate: https://slsa.dev/provenance/v1, issuer: https://token.actions.githubusercontent.com). The attestation's sha512 subject digest matches the tarball bytes we streamed, so it describes this exact artifact. This is the strongest supply chain integrity signal.
v4.0.142
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.141
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.140
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.139
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.138
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.137
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.136
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.135
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.134
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.133
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.132
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.131
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.130
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.129
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.128
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.127
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.126
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.125
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.