Add OpenAI Agents, Strands Agents, and Claude Managed Agents Guard examples

[davidmytton]

Summary

Adds three standalone JavaScript Guard agent examples and updates the repository catalog:

• examples/openai-agent — OpenAI Agents JS (@openai/agents@0.17.0) with @arcjet/guard/openai-agents/v0 (guardTool, inbound screen before run())
• examples/strands-agent — Strands Agents JS (@strands-agents/sdk@1.14.0) with @arcjet/guard/strands-agents/v1 (guardTool + guardHooks plugin)
• examples/claude-managed-agent — Claude Managed Agents hosted harness (@anthropic-ai/sdk@0.123.0) with vendored @arcjet/guard/claude-managed-agents/v0 from arcjet-js cb35c8f9 (unpublished adapter + @arcjet/transport/http2)

Each example follows existing agent demo conventions: support-agent scenario, caller-owned correlation id, fail-closed guard errors, HTML demo page, Docker/compose/devcontainer, and npm run typecheck.

Catalog updates

• Root README.md Use cases list
• Root compose.yaml includes for all three examples (alpha order)
• scripts/prepare-to-publish.ts workspaces array

Compared existing JS Guard integrations in the repo against the README; all other agent examples were already listed — only these three were missing.

Review follow-up

• Claude Managed: wait for session.status_idle with stop_reason.type === "end_turn" (not requires_action); abort the SSE stream in finally; serialize agent/environment creation.
• Strands: collect tool results (including Guard denials) from agent.messages.
• OpenAI: OpenAIProvider / Runner imported from @openai/agents (no nested @openai/agents-openai import); typed RunItem tool-output collection.
• OpenAI/Strands HTTP servers: pathname routing, JSON 400s, PORT validation.

Verification

cd examples/openai-agent && npm ci && npm run typecheck   # pass
cd examples/strands-agent && npm ci && npm run typecheck  # pass
cd examples/claude-managed-agent && npm ci && npm run typecheck  # pass

Notes

• OpenAI + Strands pin @arcjet/guard@1.11.0 (published adapters).
• Claude Managed vendors Guard + Transport (same pattern as google-adk-agent / tanstack-agent) until @arcjet/guard/claude-managed-agents/v0 ships on npm.

  

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​anthropic-ai/​sdk@​0.123.0
	npm/​@​strands-agents/​sdk@​1.14.0
	npm/​@​openai/​agents@​0.17.0

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Potential security risk (AI signal): npm @anthropic-ai/sdk is 70.0% likely risky Notes: This module itself contains no direct malicious logic (no eval/obfuscation/stealthy exfiltration), but it performs a high-impact supply-chain action: it delegates execution to code fetched from a hardcoded remote .tgz via npx at runtime. It also forwards arbitrary extra CLI arguments to that delegated execution without validation. This pattern warrants strict artifact pinning/integrity verification and review of the fetched migration package’s behavior before use in production. Confidence: 0.70 Severity: 0.70 From: examples/claude-managed-agent/package-lock.json → npm/@anthropic-ai/sdk@0.123.0 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: An AI system identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@anthropic-ai/sdk@0.123.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Potential security risk (AI signal): npm @strands-agents/sdk is 78.0% likely risky Notes: This module provides a persistent interactive bash execution capability that directly injects caller-controlled input.command into bash stdin without escaping or allowlisting, and it inherits process.env into the shell. While there is no explicit covert malware behavior in the snippet, the design constitutes an extremely high-risk execution primitive (potential RCE and data exfiltration via command output), especially if input.command is attacker-influenced. The primary correctness gap is lack of sanitization/sandboxing and reliance on a fragile sentinel substring for completion. Confidence: 0.78 Severity: 0.92 From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: An AI system identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@strands-agents/sdk@1.14.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Potential code anomaly (AI signal): npm @anthropic-ai/sdk is 97.0% likely to have a medium risk anomaly Notes: The code is a readable implementation of an agent toolset with intentionally powerful Bash and filesystem capabilities. It does not show evidence of malware or covert supply-chain behavior. Its principal risks are inherent command execution, possible exposure of non-ANTHROPIC environment secrets to executed commands, and regular-expression denial of service in the grep fallback. Use only with a trusted caller and appropriately restricted process privileges and environment. Confidence: 0.97 Severity: 0.67 From: examples/claude-managed-agent/package-lock.json → npm/@anthropic-ai/sdk@0.123.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@anthropic-ai/sdk@0.123.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Potential code anomaly (AI signal): npm @strands-agents/sdk is 66.0% likely to have a medium risk anomaly Notes: This code is a local execution “sandbox” wrapper that resolves filesystem paths under process.cwd (but allows absolute paths) and spawns sh -c to run either a provided shell command or base64-decoded source code piped into a locally invoked language interpreter. It does not show data exfiltration or covert behavior, but it has inherently high security impact: if caller-controlled inputs reach executeStreaming/executeCodeStreaming/writeFile/removeFile, it can lead to shell injection/RCE and arbitrary filesystem access for the privileges of the running process. Confidence: 0.66 Severity: 0.58 From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@strands-agents/sdk@1.14.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		System shell access: npm @aws-sdk/credential-provider-process in module node:child_process Module: node:child_process Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/credential-provider-process@3.972.70 ℹ Read more on: This package | This alert | What is shell access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-process@3.972.70. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @modelcontextprotocol/client in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: examples/openai-agent/package-lock.json → npm/@openai/agents@0.17.0 → npm/@modelcontextprotocol/client@2.0.0 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@modelcontextprotocol/client@2.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @openai/agents-core in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: examples/openai-agent/package-lock.json → npm/@openai/agents@0.17.0 → npm/@openai/agents-core@0.17.0 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@openai/agents-core@0.17.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @openai/agents-openai in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: examples/openai-agent/package-lock.json → npm/@openai/agents@0.17.0 → npm/@openai/agents-openai@0.17.0 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@openai/agents-openai@0.17.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @openai/agents-realtime in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: examples/openai-agent/package-lock.json → npm/@openai/agents@0.17.0 → npm/@openai/agents-realtime@0.17.0 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@openai/agents-realtime@0.17.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @smithy/credential-provider-imds in module node:http Module: node:http Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@smithy/credential-provider-imds@4.5.2 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@smithy/credential-provider-imds@4.5.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Environment variable access: npm @aws-sdk/credential-provider-env Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/credential-provider-env@3.972.70 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-env@3.972.70. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Environment variable access: npm @aws-sdk/credential-provider-http Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/credential-provider-http@3.972.72 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-http@3.972.72. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Filesystem access: npm @aws-sdk/credential-provider-http with module node:fs/promises Module: node:fs/promises Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/credential-provider-http@3.972.72 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-http@3.972.72. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Environment variable access: npm @aws-sdk/credential-provider-login reads AWS_REGION Env Vars: AWS_REGION Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/credential-provider-login@3.972.77 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-login@3.972.77. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Environment variable access: npm @aws-sdk/credential-provider-login reads AWS_LOGIN_CACHE_DIRECTORY Env Vars: AWS_LOGIN_CACHE_DIRECTORY Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/credential-provider-login@3.972.77 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-login@3.972.77. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Filesystem access: npm @aws-sdk/credential-provider-login with module node:fs Module: node:fs Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/credential-provider-login@3.972.77 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-login@3.972.77. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Environment variable access: npm @aws-sdk/credential-provider-node Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/credential-provider-node@3.972.82 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/credential-provider-node@3.972.82. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Environment variable access: npm @aws-sdk/token-providers Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/token-providers@3.1116.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/token-providers@3.1116.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Filesystem access: npm @aws-sdk/token-providers with module node:fs Module: node:fs Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/token-providers@3.1116.0 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/token-providers@3.1116.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Environment variable access: npm @aws-sdk/token-providers Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/token-providers@3.1125.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/token-providers@3.1125.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Filesystem access: npm @aws-sdk/token-providers with module node:fs Module: node:fs Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@aws-sdk/token-providers@3.1125.0 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aws-sdk/token-providers@3.1125.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Environment variable access: npm @openai/agents-core Location: Package overview From: examples/openai-agent/package-lock.json → npm/@openai/agents@0.17.0 → npm/@openai/agents-core@0.17.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@openai/agents-core@0.17.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Environment variable access: npm @smithy/credential-provider-imds Location: Package overview From: examples/strands-agent/package-lock.json → npm/@strands-agents/sdk@1.14.0 → npm/@smithy/credential-provider-imds@4.5.2 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@smithy/credential-provider-imds@4.5.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[arcjet-review]

Arcjet Review — 🔴 High Risk

Decision: Cannot Assess

Rationale: Review failed due to an internal error: unknown error. Escalating to human reviewers.

_{Review: 61f3359e | Powered by Arcjet Review}

[arcjet-review]

Arcjet Review — 🔴 High Risk

Decision: Cannot Assess

Rationale: Review failed due to an internal error: unknown error. Escalating to human reviewers.

_{Review: 6721f197 | Powered by Arcjet Review}