← Home

@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.

100
Versions
SEE LICENSE IN README.md
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

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

Keywords

aiagentsdkclaudeanthropicautomationcode-generation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 of 185)

Version Deps Published
0.2.141 2 / 0
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
0.2.75 0 / 0
0.2.74 0 / 0
0.2.73 0 / 0
0.2.72 0 / 0
0.2.71 0 / 0
0.2.70 0 / 0
0.2.69 0 / 0
0.2.68 0 / 0
0.2.66 0 / 0
0.2.64 0 / 0
0.2.63 0 / 0
0.2.62 0 / 0
0.2.61 0 / 0
0.2.59 0 / 0
0.2.58 0 / 0
0.2.56 0 / 0
0.2.55 0 / 0
0.2.54 0 / 0
0.2.53 0 / 0
0.2.52 0 / 0
0.2.51 0 / 0
0.2.50 0 / 0
0.2.49 0 / 0
0.2.48 0 / 0
0.2.47 0 / 0
0.2.45 0 / 0
0.2.44 0 / 0
0.2.42 0 / 0
0.2.41 0 / 0
0.2.40 0 / 0
0.2.39 0 / 0
0.2.38 0 / 0
0.2.37 0 / 0
0.2.36 0 / 0
0.2.34 0 / 0
0.2.33 0 / 0
0.2.32 0 / 0
0.2.31 0 / 0
0.2.30 0 / 0
0.2.29 0 / 0
0.2.27 0 / 0
0.2.26 0 / 0
0.2.25 0 / 0
0.2.23 0 / 0
0.2.22 0 / 0
0.2.21 0 / 0
0.2.20 0 / 0
0.2.19 0 / 0
Showing 100 of 185 Next page →

v0.2.141

1 finding
INFO No provenance attestation provenance

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

v0.2.140

1 finding
INFO No provenance attestation provenance

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

v0.2.139

1 finding
INFO No provenance attestation provenance

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

v0.2.138

1 finding
INFO No provenance attestation provenance

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

v0.2.137

1 finding
INFO No provenance attestation provenance

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

v0.2.136

1 finding
INFO No provenance attestation provenance

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

v0.2.133

1 finding
INFO No provenance attestation provenance

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

v0.2.132

1 finding
INFO No provenance attestation provenance

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

v0.2.131

1 finding
INFO No provenance attestation provenance

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

v0.2.129

1 finding
INFO No provenance attestation provenance

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

v0.2.128

1 finding
INFO No provenance attestation provenance

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

v0.2.126

1 finding
INFO No provenance attestation provenance

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

v0.2.124

1 finding
INFO No provenance attestation provenance

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

v0.2.123

1 finding
INFO No provenance attestation provenance

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

v0.2.122

1 finding
INFO No provenance attestation provenance

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

v0.2.121

1 finding
INFO No provenance attestation provenance

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

v0.2.120

3 findings
HIGH Long encoded string in modified file: assistant.mjs source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: bridge.mjs source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.2.119

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.2.118

1 finding
INFO No provenance attestation provenance

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

v0.2.117

1 finding
INFO No provenance attestation provenance

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

v0.2.116

1 finding
INFO No provenance attestation provenance

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

v0.2.114

1 finding
INFO No provenance attestation provenance

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

v0.2.113

1 finding
INFO No provenance attestation provenance

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

v0.2.112

2 findings
HIGH Long encoded string in modified file: cli.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

INFO No provenance attestation provenance

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

v0.2.111

2 findings
HIGH Long encoded string in modified file: cli.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

INFO No provenance attestation provenance

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

v0.2.110

2 findings
HIGH Long encoded string in modified file: cli.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

INFO No provenance attestation provenance

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

v0.2.109

2 findings
HIGH Long encoded string in modified file: cli.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

INFO No provenance attestation provenance

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

v0.2.108

2 findings
HIGH Long encoded string in modified file: cli.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

INFO No provenance attestation provenance

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

v0.2.107

2 findings
HIGH Long encoded string in modified file: cli.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

INFO No provenance attestation provenance

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

v0.2.105

2 findings
HIGH Long encoded string in modified file: cli.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

INFO No provenance attestation provenance

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

v0.2.104

2 findings
HIGH Long encoded string in modified file: cli.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

INFO No provenance attestation provenance

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

v0.2.101

2 findings
HIGH Long encoded string in modified file: cli.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

INFO No provenance attestation provenance

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

v0.2.100

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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 findings
HIGH Bundled binary files (12) npm-metadata

Package 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

INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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 findings
HIGH Bundled binary files (12) npm-metadata

Package 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

INFO No provenance attestation provenance

[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 findings
HIGH Bundled binary files (12) npm-metadata

Package 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

INFO No provenance attestation provenance

[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 findings
HIGH Bundled binary files (12) npm-metadata

Package 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

INFO No provenance attestation provenance

[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 findings
HIGH Bundled binary files (12) npm-metadata

Package 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

INFO No provenance attestation provenance

[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 findings
HIGH Bundled binary files (12) npm-metadata

Package 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

INFO No provenance attestation provenance

[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 findings
HIGH Bundled binary files (12) npm-metadata

Package 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

INFO No provenance attestation provenance

[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 findings
HIGH Bundled binary files (12) npm-metadata

Package 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

INFO No provenance attestation provenance

[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 findings
HIGH Bundled binary files (18) npm-metadata

Package 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

INFO No provenance attestation provenance

[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 findings
HIGH Bundled binary files (18) npm-metadata

Package 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

INFO No provenance attestation provenance

[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 findings
HIGH New obfuscated file: browser-sdk.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: browser-sdk.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: bridge.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: bridge.mjs source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

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

v0.2.80

3 findings
HIGH New obfuscated file: browser-sdk.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: browser-sdk.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

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

v0.2.79

3 findings
HIGH New obfuscated file: browser-sdk.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: browser-sdk.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

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

v0.2.78

3 findings
HIGH New obfuscated file: browser-sdk.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: browser-sdk.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

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

v0.2.77

3 findings
HIGH New obfuscated file: browser-sdk.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: browser-sdk.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

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

v0.2.76

3 findings
HIGH New obfuscated file: browser-sdk.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: browser-sdk.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

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

v0.2.75

1 finding
INFO No provenance attestation provenance

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

v0.2.74

1 finding
INFO No provenance attestation provenance

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

v0.2.73

1 finding
INFO No provenance attestation provenance

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

v0.2.72

1 finding
INFO No provenance attestation provenance

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

v0.2.71

1 finding
INFO No provenance attestation provenance

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

v0.2.70

1 finding
INFO No provenance attestation provenance

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

v0.2.69

1 finding
INFO No provenance attestation provenance

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

v0.2.68

1 finding
INFO No provenance attestation provenance

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

v0.2.66

1 finding
INFO No provenance attestation provenance

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

v0.2.64

1 finding
INFO No provenance attestation provenance

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

v0.2.63

1 finding
INFO No provenance attestation provenance

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

v0.2.62

1 finding
INFO No provenance attestation provenance

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

v0.2.61

1 finding
INFO No provenance attestation provenance

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

v0.2.59

1 finding
INFO No provenance attestation provenance

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

v0.2.58

1 finding
INFO No provenance attestation provenance

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

v0.2.56

1 finding
INFO No provenance attestation provenance

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

v0.2.55

1 finding
INFO No provenance attestation provenance

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

v0.2.54

1 finding
INFO No provenance attestation provenance

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

v0.2.53

1 finding
INFO No provenance attestation provenance

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

v0.2.52

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if(Y.s&&$[B]==="."){W+=G?`${$[B]}\r 54 | `:`[${$[B]}\r > 55 | ]`;continue}if(W+=$[B],$[B]==="\\")J=!0;else if(G&&$[B]==="]")G=!1;else if(!G&&$[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else N7.streamInput(Q);return N7}function Fx(Q){return DQ(Q)}function Lx(Q,X){return FW(Q,X)}async function Nx(Q,X){l

INFO No provenance attestation provenance

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

v0.2.51

1 finding
INFO No provenance attestation provenance

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

v0.2.50

2 findings
HIGH env-spread: sdk.mjs:66 semgrep

Spreading entire process.env into an object — may capture all secrets 64 | ]))`;continue}}if($.s&&Y[z]==="."){G+=W?`${Y[z]}\r 65 | `:`[${Y[z]}\r > 66 | ]`;continue}if(G+=Y[z],Y[z]==="\\")J=!0;else if(W&&Y[z]==="]")W=!1;else if(!W&&Y[z]==="[")W=!0}try{new RegExp(G)}catch{r 67 | `);else A7.streamInput(Q);return A7}function $m(Q){return wX(Q)}function Ym(Q,X){return aJ(Q,X)}async function Gm(Q,X){l

INFO No provenance attestation provenance

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

v0.2.49

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if(Y.s&&$[B]==="."){W+=G?`${$[B]}\r 54 | `:`[${$[B]}\r > 55 | ]`;continue}if(W+=$[B],$[B]==="\\")J=!0;else if(G&&$[B]==="]")G=!1;else if(!G&&$[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else K7.streamInput(Q);return K7}function tT(Q){return UQ(Q)}function aT(Q,X){return BW(Q,X)}async function sT(Q,X){l

INFO No provenance attestation provenance

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

v0.2.48

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if(Y.s&&$[B]==="."){W+=G?`${$[B]}\r 54 | `:`[${$[B]}\r > 55 | ]`;continue}if(W+=$[B],$[B]==="\\")J=!0;else if(G&&$[B]==="]")G=!1;else if(!G&&$[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else K7.streamInput(Q);return K7}function tT(Q){return UQ(Q)}function aT(Q,X){return BW(Q,X)}async function sT(Q,X){l

INFO No provenance attestation provenance

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

v0.2.47

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if(Y.s&&$[B]==="."){W+=G?`${$[B]}\r 54 | `:`[${$[B]}\r > 55 | ]`;continue}if(W+=$[B],$[B]==="\\")J=!0;else if(G&&$[B]==="]")G=!1;else if(!G&&$[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else K7.streamInput(Q);return K7}function tT(Q){return UQ(Q)}function aT(Q,X){return BW(Q,X)}async function sT(Q,X){l

INFO No provenance attestation provenance

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

v0.2.45

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if(Y.s&&$[B]==="."){W+=G?`${$[B]}\r 54 | `:`[${$[B]}\r > 55 | ]`;continue}if(W+=$[B],$[B]==="\\")J=!0;else if(G&&$[B]==="]")G=!1;else if(!G&&$[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else V7.streamInput(Q);return V7}function Qx(Q){return LQ(Q)}function Xx(Q,X){return KW(Q,X)}async function Yx(Q,X){l

INFO No provenance attestation provenance

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

v0.2.44

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if(Y.s&&$[B]==="."){W+=G?`${$[B]}\r 54 | `:`[${$[B]}\r > 55 | ]`;continue}if(W+=$[B],$[B]==="\\")J=!0;else if(G&&$[B]==="]")G=!1;else if(!G&&$[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(Q);return z7}function eT(Q){return qQ(Q)}function Qx(Q,X){return KW(Q,X)}async function Xx(Q,X){l

INFO No provenance attestation provenance

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

v0.2.42

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if(Y.s&&$[B]==="."){W+=G?`${$[B]}\r 54 | `:`[${$[B]}\r > 55 | ]`;continue}if(W+=$[B],$[B]==="\\")J=!0;else if(G&&$[B]==="]")G=!1;else if(!G&&$[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(Q);return z7}function eT(Q){return qQ(Q)}function Qx(Q,X){return KW(Q,X)}async function Xx(Q,X){l

INFO No provenance attestation provenance

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

v0.2.41

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else K7.streamInput(X);return K7}function Yx(X){return L9(X)}function Wx(X,Q){return VW(X,Q)}async function Jx(X,Q){l

INFO No provenance attestation provenance

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

v0.2.40

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else K7.streamInput(X);return K7}function $x(X){return L9(X)}function Yx(X,Q){return VW(X,Q)}async function Wx(X,Q){l

INFO No provenance attestation provenance

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

v0.2.39

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else K7.streamInput(X);return K7}function $x(X){return L9(X)}function Yx(X,Q){return VW(X,Q)}async function Wx(X,Q){l

INFO No provenance attestation provenance

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

v0.2.38

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else K7.streamInput(X);return K7}function $x(X){return L9(X)}function Yx(X,Q){return VW(X,Q)}async function Wx(X,Q){l

INFO No provenance attestation provenance

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

v0.2.37

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function e_(X){return V9(X)}function Xx(X,Q){return UW(X,Q)}async function Qx(X,Q){l

INFO No provenance attestation provenance

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

v0.2.36

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function e_(X){return V9(X)}function Xx(X,Q){return UW(X,Q)}async function Qx(X,Q){l

INFO No provenance attestation provenance

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

v0.2.34

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function e_(X){return V9(X)}function Xx(X,Q){return UW(X,Q)}async function Qx(X,Q){l

INFO No provenance attestation provenance

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

v0.2.33

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function e_(X){return V9(X)}function Xx(X,Q){return UW(X,Q)}async function Qx(X,Q){l

INFO No provenance attestation provenance

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

v0.2.32

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function s_(X){return V9(X)}function e_(X,Q){return UW(X,Q)}async function Xx(X,Q){l

INFO No provenance attestation provenance

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

v0.2.31

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function s_(X){return V9(X)}function e_(X,Q){return UW(X,Q)}async function Xx(X,Q){l

INFO No provenance attestation provenance

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

v0.2.30

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function s_(X){return V9(X)}function e_(X,Q){return UW(X,Q)}async function Xx(X,Q){l

INFO No provenance attestation provenance

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

v0.2.29

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function t_(X){return V9(X)}function a_(X,Q){return UW(X,Q)}async function s_(X,Q){l

INFO No provenance attestation provenance

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

v0.2.27

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function t_(X){return V9(X)}function a_(X,Q){return UW(X,Q)}async function s_(X,Q){l

INFO No provenance attestation provenance

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

v0.2.26

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function t_(X){return V9(X)}function a_(X,Q){return UW(X,Q)}async function s_(X,Q){l

INFO No provenance attestation provenance

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

v0.2.25

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function t_(X){return V9(X)}function a_(X,Q){return UW(X,Q)}async function s_(X,Q){l

INFO No provenance attestation provenance

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

v0.2.23

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function t_(X){return V9(X)}function a_(X,Q){return UW(X,Q)}async function s_(X,Q){l

INFO No provenance attestation provenance

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

v0.2.22

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function t_(X){return V9(X)}function a_(X,Q){return KW(X,Q)}async function s_(X,Q){l

INFO No provenance attestation provenance

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

v0.2.21

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function t_(X){return V9(X)}function a_(X,Q){return KW(X,Q)}async function s_(X,Q){l

INFO No provenance attestation provenance

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

v0.2.20

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function o_(X){return V9(X)}function t_(X,Q){return KW(X,Q)}async function a_(X,Q){l

INFO No provenance attestation provenance

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

v0.2.19

2 findings
HIGH env-spread: sdk.mjs:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | ]))`;continue}}if($.s&&Y[B]==="."){W+=G?`${Y[B]}\r 54 | `:`[${Y[B]}\r > 55 | ]`;continue}if(W+=Y[B],Y[B]==="\\")J=!0;else if(G&&Y[B]==="]")G=!1;else if(!G&&Y[B]==="[")G=!0}try{new RegExp(W)}catch{r 56 | `);else z7.streamInput(X);return z7}function p_(X){return V9(X)}function d_(X,Q){return zW(X,Q)}async function i_(X,Q){l

INFO No provenance attestation provenance

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