@anthropic-ai/claude-agent-sdk
SDK for building AI agents with Claude Code's capabilities. Programmatically interact with Claude to build autonomous agents that can understand codebases, edit files, and execute workflows.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:bridge.mjs | AI (source-diff): Standard bundler output for bridge module; copyright header matches Anthropic; expected for SDK bundle. | ai | |
| source-diff | net-exec-file:bridge.mjs | AI (source-diff): Agent SDK bridge module legitimately requires network and execution capabilities; official Anthropic package. | ai | |
| source-diff | obfuscated-file:browser-sdk.js | AI (source-diff): browser-sdk.js is a legitimate bundled/minified browser entry point with Anthropic copyright header; standard for browser-targeted SDK bundles. | ai | |
| source-diff | net-exec-file:browser-sdk.js | AI (source-diff): Browser SDK bundle naturally contains network calls (API client) and dynamic code patterns from bundled validators (Ajv/Zod); not malicious. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() in minified SDK bundle is standard JavaScript bundler output; no malicious context. Stable false positive for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Bundled AJV JSON schema validator uses new Function() for compiled validators — well-known pattern, not a risk. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Standard pattern for spawning Claude Code subprocess with inherited environment. Expected for this SDK. | ai | |
| source-diff | encoded-string-file:cli.js | AI (source-diff): Bundled/minified CLI code with standard tool-parsing and utility logic; not obfuscated malicious payloads. Stable for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Bundled ripgrep and audio-capture binaries are expected for a code agent SDK needing fast search and audio input across platforms. Official Anthropic package. | ai | |
| source-diff | encoded-string-file:bridge.mjs | AI (source-diff): Bundled/minified SDK output containing git utility code. Standard for this package's build process. | ai | |
| source-diff | encoded-string-file:assistant.mjs | AI (source-diff): Bundled/minified SDK output containing inlined dependencies like mime-types. Standard for this package's build process. | ai | |
| provenance | no-provenance | AI (provenance): Established Anthropic package; no provenance is a minor gap, not a risk signal. | ai |
Versions (showing 51 of 184)
| Version | Deps | Published |
|---|---|---|
| 0.2.140 | 2 / 0 | |
| 0.2.139 | 2 / 0 | |
| 0.2.138 | 2 / 0 | |
| 0.2.137 | 2 / 0 | |
| 0.2.136 | 2 / 0 | |
| 0.2.133 | 2 / 0 | |
| 0.2.132 | 2 / 0 | |
| 0.2.131 | 2 / 0 | |
| 0.2.129 | 2 / 0 | |
| 0.2.128 | 2 / 0 | |
| 0.2.126 | 2 / 0 | |
| 0.2.124 | 2 / 0 | |
| 0.2.123 | 2 / 0 | |
| 0.2.122 | 2 / 0 | |
| 0.2.121 | 2 / 0 | |
| 0.2.120 | 2 / 0 | |
| 0.2.119 | 2 / 0 | |
| 0.2.118 | 2 / 0 | |
| 0.2.117 | 2 / 0 | |
| 0.2.116 | 2 / 0 | |
| 0.2.114 | 2 / 0 | |
| 0.2.113 | 2 / 0 | |
| 0.2.112 | 2 / 0 | |
| 0.2.111 | 2 / 0 | |
| 0.2.110 | 2 / 0 | |
| 0.2.109 | 2 / 0 | |
| 0.2.108 | 2 / 0 | |
| 0.2.107 | 2 / 0 | |
| 0.2.105 | 2 / 0 | |
| 0.2.104 | 2 / 0 | |
| 0.2.101 | 2 / 0 | |
| 0.2.100 | 2 / 0 | |
| 0.2.98 | 2 / 0 | |
| 0.2.97 | 2 / 0 | |
| 0.2.96 | 2 / 0 | |
| 0.2.94 | 2 / 0 | |
| 0.2.92 | 2 / 0 | |
| 0.2.91 | 2 / 0 | |
| 0.2.90 | 2 / 0 | |
| 0.2.89 | 2 / 0 | |
| 0.2.87 | 2 / 0 | |
| 0.2.86 | 2 / 0 | |
| 0.2.85 | 0 / 0 | |
| 0.2.84 | 0 / 0 | |
| 0.2.83 | 0 / 0 | |
| 0.2.81 | 0 / 0 | |
| 0.2.80 | 0 / 0 | |
| 0.2.79 | 0 / 0 | |
| 0.2.78 | 0 / 0 | |
| 0.2.77 | 0 / 0 | |
| 0.2.76 | 0 / 0 |
v0.2.140
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.139
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.138
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.137
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.136
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.133
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.132
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.131
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.129
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.126
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.120
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.112
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.111
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.110
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.109
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.108
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.107
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.105
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.104
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.101
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.97
2 findingsPackage contains compiled binaries that could be backdoors: • vendor/ripgrep/arm64-darwin/rg • vendor/ripgrep/arm64-linux/rg • vendor/ripgrep/x64-darwin/rg • vendor/ripgrep/x64-linux/rg • vendor/ripgrep/arm64-win32/rg.exe • vendor/ripgrep/x64-win32/rg.exe • vendor/audio-capture/arm64-darwin/audio-capture.node • vendor/audio-capture/arm64-linux/audio-capture.node • vendor/audio-capture/arm64-win32/audio-capture.node • vendor/audio-capture/x64-darwin/audio-capture.node ... and 2 more
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.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.
v0.2.92
2 findingsPackage contains compiled binaries that could be backdoors: • vendor/ripgrep/arm64-darwin/rg • vendor/ripgrep/arm64-linux/rg • vendor/ripgrep/x64-darwin/rg • vendor/ripgrep/x64-linux/rg • vendor/ripgrep/arm64-win32/rg.exe • vendor/ripgrep/x64-win32/rg.exe • vendor/audio-capture/arm64-darwin/audio-capture.node • vendor/audio-capture/arm64-linux/audio-capture.node • vendor/audio-capture/arm64-win32/audio-capture.node • vendor/audio-capture/x64-darwin/audio-capture.node ... and 2 more
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.91
2 findingsPackage contains compiled binaries that could be backdoors: • vendor/ripgrep/arm64-darwin/rg • vendor/ripgrep/arm64-linux/rg • vendor/ripgrep/x64-darwin/rg • vendor/ripgrep/x64-linux/rg • vendor/ripgrep/arm64-win32/rg.exe • vendor/ripgrep/x64-win32/rg.exe • vendor/audio-capture/arm64-darwin/audio-capture.node • vendor/audio-capture/arm64-linux/audio-capture.node • vendor/audio-capture/arm64-win32/audio-capture.node • vendor/audio-capture/x64-darwin/audio-capture.node ... and 2 more
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.90
2 findingsPackage contains compiled binaries that could be backdoors: • vendor/ripgrep/arm64-darwin/rg • vendor/ripgrep/arm64-linux/rg • vendor/ripgrep/x64-darwin/rg • vendor/ripgrep/x64-linux/rg • vendor/ripgrep/arm64-win32/rg.exe • vendor/ripgrep/x64-win32/rg.exe • vendor/audio-capture/arm64-darwin/audio-capture.node • vendor/audio-capture/arm64-linux/audio-capture.node • vendor/audio-capture/arm64-win32/audio-capture.node • vendor/audio-capture/x64-darwin/audio-capture.node ... and 2 more
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.89
2 findingsPackage contains compiled binaries that could be backdoors: • vendor/ripgrep/arm64-darwin/rg • vendor/ripgrep/arm64-linux/rg • vendor/ripgrep/x64-darwin/rg • vendor/ripgrep/x64-linux/rg • vendor/ripgrep/arm64-win32/rg.exe • vendor/ripgrep/x64-win32/rg.exe • vendor/audio-capture/arm64-darwin/audio-capture.node • vendor/audio-capture/arm64-linux/audio-capture.node • vendor/audio-capture/arm64-win32/audio-capture.node • vendor/audio-capture/x64-darwin/audio-capture.node ... and 2 more
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.87
2 findingsPackage contains compiled binaries that could be backdoors: • vendor/ripgrep/arm64-darwin/rg • vendor/ripgrep/arm64-linux/rg • vendor/ripgrep/x64-darwin/rg • vendor/ripgrep/x64-linux/rg • vendor/ripgrep/arm64-win32/rg.exe • vendor/ripgrep/x64-win32/rg.exe • vendor/audio-capture/arm64-darwin/audio-capture.node • vendor/audio-capture/arm64-linux/audio-capture.node • vendor/audio-capture/arm64-win32/audio-capture.node • vendor/audio-capture/x64-darwin/audio-capture.node ... and 2 more
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.86
2 findingsPackage contains compiled binaries that could be backdoors: • vendor/ripgrep/arm64-darwin/rg • vendor/ripgrep/arm64-linux/rg • vendor/ripgrep/x64-darwin/rg • vendor/ripgrep/x64-linux/rg • vendor/ripgrep/arm64-win32/rg.exe • vendor/ripgrep/x64-win32/rg.exe • vendor/audio-capture/arm64-darwin/audio-capture.node • vendor/audio-capture/arm64-linux/audio-capture.node • vendor/audio-capture/arm64-win32/audio-capture.node • vendor/audio-capture/x64-darwin/audio-capture.node ... and 2 more
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.85
2 findingsPackage contains compiled binaries that could be backdoors: • vendor/ripgrep/arm64-darwin/rg • vendor/ripgrep/arm64-linux/rg • vendor/ripgrep/x64-darwin/rg • vendor/ripgrep/x64-linux/rg • vendor/ripgrep/arm64-win32/rg.exe • vendor/ripgrep/x64-win32/rg.exe • vendor/audio-capture/arm64-darwin/audio-capture.node • vendor/audio-capture/arm64-linux/audio-capture.node • vendor/audio-capture/arm64-win32/audio-capture.node • vendor/audio-capture/x64-darwin/audio-capture.node ... and 2 more
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.84
2 findingsPackage contains compiled binaries that could be backdoors: • vendor/ripgrep/arm64-darwin/rg • vendor/ripgrep/arm64-linux/rg • vendor/ripgrep/x64-darwin/rg • vendor/ripgrep/x64-linux/rg • vendor/ripgrep/arm64-win32/rg.exe • vendor/ripgrep/x64-win32/rg.exe • vendor/audio-capture/arm64-darwin/audio-capture.node • vendor/audio-capture/arm64-linux/audio-capture.node • vendor/audio-capture/arm64-win32/audio-capture.node • vendor/audio-capture/x64-darwin/audio-capture.node ... and 8 more
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.83
2 findingsPackage contains compiled binaries that could be backdoors: • vendor/ripgrep/arm64-darwin/rg • vendor/ripgrep/arm64-linux/rg • vendor/ripgrep/x64-darwin/rg • vendor/ripgrep/x64-linux/rg • vendor/ripgrep/arm64-win32/rg.exe • vendor/ripgrep/x64-win32/rg.exe • vendor/audio-capture/arm64-darwin/audio-capture.node • vendor/audio-capture/arm64-linux/audio-capture.node • vendor/audio-capture/arm64-win32/audio-capture.node • vendor/audio-capture/x64-darwin/audio-capture.node ... and 8 more
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.81
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.80
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.79
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.78
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.77
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.76
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.