@anthropic-ai/bedrock-sdk
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from individual to GitHub Actions CI/CD; SLSA provenance confirms legitimate automated publishing. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Anthropic org rotation; removals consistent with team changes at official publisher. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Anthropic org rotation; new maintainer has anthropic- suffix indicating internal team member. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase consistent with major feature additions across 9 skipped minor versions of an official Anthropic SDK. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large version jump from 0.12.6 to 0.21.1; new files reflect legitimate SDK expansion, not injected code. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): The env spread in core/auth.js is a snapshot-for-restoration pattern in a withTempEnv helper — standard practice for temporarily modifying env vars. No exfiltration risk; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@aws-sdk/client-bedrock-runtime | AI (dependencies): @aws-sdk/client-bedrock-runtime is the official AWS SDK v3 Bedrock client; its use is expected and stable for this Bedrock integration package. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 0.32.0 | 11 / 0 | |
| 0.31.0 | 11 / 0 | |
| 0.30.2 | 11 / 0 | |
| 0.30.1 | 11 / 0 | |
| 0.30.0 | 11 / 0 | |
| 0.29.2 | 11 / 0 | |
| 0.29.1 | 11 / 0 | |
| 0.29.0 | 11 / 0 | |
| 0.28.1 | 11 / 0 | |
| 0.28.0 | 11 / 0 | |
| 0.27.0 | 11 / 0 | |
| 0.26.4 | 11 / 0 | |
| 0.26.3 | 11 / 0 | |
| 0.26.2 | 11 / 0 | |
| 0.26.0 | 11 / 0 | |
| 0.25.0 | 11 / 0 | |
| 0.24.0 | 11 / 0 | |
| 0.23.0 | 11 / 0 | |
| 0.22.4 | 11 / 0 | |
| 0.22.3 | 11 / 0 | |
| 0.22.2 | 11 / 0 | |
| 0.22.1 | 11 / 0 | |
| 0.22.0 | 11 / 0 | |
| 0.21.2 | 11 / 0 | |
| 0.21.1 | 11 / 0 | |
| 0.21.0 | 11 / 0 | |
| 0.12.6 | 11 / 0 | |
| 0.12.5 | 11 / 0 | |
| 0.12.4 | 11 / 0 | |
| 0.12.0 | 11 / 0 | |
| 0.11.2 | 11 / 0 | |
| 0.11.1 | 11 / 0 | |
| 0.11.0 | 11 / 0 | |
| 0.10.4 | 11 / 0 | |
| 0.10.3 | 11 / 0 | |
| 0.10.2 | 11 / 0 | |
| 0.10.1 | 11 / 0 | |
| 0.10.0 | 12 / 0 | |
| 0.9.8 | 12 / 0 | |
| 0.9.7 | 12 / 0 | |
| 0.9.6 | 12 / 0 | |
| 0.9.5 | 12 / 0 | |
| 0.9.4 | 12 / 0 | |
| 0.9.3 | 12 / 0 | |
| 0.9.2 | 12 / 0 | |
| 0.9.1 | 12 / 0 | |
| 0.9.0 | 12 / 0 | |
| 0.8.0 | 12 / 0 | |
| 0.7.1 | 12 / 0 | |
| 0.7.0 | 12 / 0 |
v0.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.