@anthropic-ai/bedrock-sdk

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

zak-anthropicdylanc-anthropicbenjmannnikhil-anthropicejlangev-antjv-anthropicollie-ant-2025packy-anthropicnoahz-anthropicsbidasariawolffiexfelixrieseberg-anthropicjoan-anthropic

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	2026/06/07
maintainer-change	maintainer-removed	AI (maintainer-change): Anthropic org rotation; removals consistent with team changes at official publisher.	ai	2026/04/27
maintainer-change	maintainer-added	AI (maintainer-change): Anthropic org rotation; new maintainer has anthropic- suffix indicating internal team member.	ai	2026/04/27
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	2026/04/27
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	2026/04/27
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	2026/04/26
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	2026/04/24

Versions (showing 36 of 36)

Version	Deps	Published
0.30.0	11 / 0	2026-06-05
0.29.2	11 / 0	2026-05-19
0.29.1	11 / 0	2026-04-30
0.29.0	11 / 0	2026-04-23
0.28.1	11 / 0	2026-04-08
0.28.0	11 / 0	2026-04-07
0.27.0	11 / 0	2026-04-01
0.26.4	11 / 0	2026-02-19
0.26.3	11 / 0	2026-02-05
0.26.2	11 / 0	2026-01-29
0.26.0	11 / 0	2025-11-18
0.25.0	11 / 0	2025-09-17
0.24.0	11 / 0	2025-08-05
0.23.0	11 / 0	2025-07-21
0.22.4	11 / 0	2025-07-03
0.22.3	11 / 0	2025-06-30
0.22.2	11 / 0	2025-06-24
0.22.1	11 / 0	2025-05-22
0.22.0	11 / 0	2025-05-15
0.21.2	11 / 0	2025-05-09
0.21.1	11 / 0	2025-05-09
0.21.0	11 / 0	2025-05-09
0.12.6	11 / 0	2025-04-28
0.12.5	11 / 0	2025-04-25
0.12.4	11 / 0	2025-01-23
0.12.0	11 / 0	2024-12-17
0.11.2	11 / 0	2024-11-05
0.11.1	11 / 0	2024-10-23
0.11.0	11 / 0	2024-10-22
0.10.4	11 / 0	2024-10-08
0.10.3	11 / 0	2024-10-04
0.10.2	11 / 0	2024-07-29
0.10.1	11 / 0	2024-06-25
0.10.0	12 / 0	2024-05-30
0.9.8	12 / 0	2024-05-16
0.9.7	12 / 0	2024-05-08

v0.30.0

2 findings

HIGH Publisher changed: packy-anthropic → GitHub Actions (on 2026-06-05) provenance

This version was published by a different npm account than previous versions on 2026-06-05. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.29.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.29.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.29.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.28.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.28.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.27.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.26.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.26.3

4 findings

HIGH env-spread: core/auth.js:113 semgrep

Spreading entire process.env into an object — may capture all secrets 111 | exports.getAuthHeaders = getAuthHeaders; 112 | const withTempEnv = async (updateEnv, fn) => { > 113 | const previousEnv = { ...process.env }; 114 | try { 115 | updateEnv();

HIGH env-spread: core/auth.mjs:73 semgrep

Spreading entire process.env into an object — may capture all secrets 71 | }; 72 | const withTempEnv = async (updateEnv, fn) => { > 73 | const previousEnv = { ...process.env }; 74 | try { 75 | updateEnv();

HIGH env-spread: src/core/auth.ts:106 semgrep

Spreading entire process.env into an object — may capture all secrets 104 | 105 | const withTempEnv = async <R>(updateEnv: () => void, fn: () => Promise<R>): Promise<R> => { > 106 | const previousEnv = { ...process.env }; 107 | 108 | try {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.26.2

4 findings

HIGH env-spread: core/auth.js:113 semgrep

Spreading entire process.env into an object — may capture all secrets 111 | exports.getAuthHeaders = getAuthHeaders; 112 | const withTempEnv = async (updateEnv, fn) => { > 113 | const previousEnv = { ...process.env }; 114 | try { 115 | updateEnv();

HIGH env-spread: core/auth.mjs:73 semgrep

Spreading entire process.env into an object — may capture all secrets 71 | }; 72 | const withTempEnv = async (updateEnv, fn) => { > 73 | const previousEnv = { ...process.env }; 74 | try { 75 | updateEnv();

HIGH env-spread: src/core/auth.ts:106 semgrep

Spreading entire process.env into an object — may capture all secrets 104 | 105 | const withTempEnv = async <R>(updateEnv: () => void, fn: () => Promise<R>): Promise<R> => { > 106 | const previousEnv = { ...process.env }; 107 | 108 | try {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.26.0

4 findings

HIGH env-spread: core/auth.js:113 semgrep

Spreading entire process.env into an object — may capture all secrets 111 | exports.getAuthHeaders = getAuthHeaders; 112 | const withTempEnv = async (updateEnv, fn) => { > 113 | const previousEnv = { ...process.env }; 114 | try { 115 | updateEnv();

HIGH env-spread: core/auth.mjs:73 semgrep

Spreading entire process.env into an object — may capture all secrets 71 | }; 72 | const withTempEnv = async (updateEnv, fn) => { > 73 | const previousEnv = { ...process.env }; 74 | try { 75 | updateEnv();

HIGH env-spread: src/core/auth.ts:106 semgrep

Spreading entire process.env into an object — may capture all secrets 104 | 105 | const withTempEnv = async <R>(updateEnv: () => void, fn: () => Promise<R>): Promise<R> => { > 106 | const previousEnv = { ...process.env }; 107 | 108 | try {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.