deps: periodic dependency update

[qw-in]

Periodic dependency and security update for the examples

[arcjet-review]

Arcjet Review — 🟡 Medium Risk

Decision: Needs Review

Rationale: This PR updates dependencies across many example applications and refreshes generated framework files. The changes are mostly version bumps, including a security-motivated override for transitive uuid usage in the express-newman example, and no hardcoded secrets or direct application security regressions are visible in the diff. However, dependency changes are an escalation trigger, the scope spans many frameworks, and some updates touch security-sensitive/example protection packages such as Arcjet guard, sensitive-info-rampart, Next.js, React Router, Firebase Functions, and pre-1.0 packages where minor version bumps can carry breaking changes. I am not confident enough to approve without human verification that installs, lockfile state, and example type/build/test suites pass.

Summary of Changes

Updates package dependencies across multiple examples, adds npm overrides to force uuid 11.1.1 under Newman/Postman transitive packages, refreshes Next.js generated type references, and regenerates the TanStack Start route tree with reordered route declarations.

Escalation Triggers

• Dependency Changes: Multiple package.json files under examples were changed, including runtime framework, security/protection, AI, and testing dependencies.

Review Focus Areas

• Verify that the nested npm overrides for postman-collection, postman-request, postman-runtime, and serialised-error correctly force uuid 11.1.1 in the actual resolved dependency tree.
  The PR references a security update for GHSA-w5hq-g745-h8pq; the mitigation should be confirmed with the package manager's installed/resolved output, not just package.json syntax.
• Review the eve 0.31.0 to 0.38.3 changelog and run the example's typecheck/build.
  For pre-1.0 packages, minor version bumps may include breaking API or behavioral changes.
• Run the Next.js example test/typecheck/build paths after the Next, React, AI SDK, React Hook Form, and Playwright updates.
  Several runtime and test dependencies move together, which can introduce compatibility issues even when each individual bump is minor or patch-level.
• Validate the React Router middleware example after updating @arcjet/react-router and React Router packages from 7.16.x to 7.18.x.
  Middleware behavior and server adapters can change across framework minor releases and may affect route protection behavior.
• Confirm the regenerated route tree was produced by the expected TanStack generator and that no routes were added, removed, or given incorrect paths.
  The generated file appears mostly reordered, but route tree generation controls application routing and should match the source route files.
• Confirm that the added .next/types/root-params.d.ts import is expected for the updated Next.js version and that clean installs/builds generate this file.
  Referencing generated files that are absent in clean environments can break typechecking.

Notes

No direct code paths for authentication, input handling, cryptography, or secret management were changed in the visible diff. The primary residual risk is dependency resolution and runtime compatibility across the affected examples.

Path filtering: 24 files excluded by ignore paths. 29 of 53 files included in review.

_{Review: 8f105b81 | Model: openai/gpt-5.5 | Powered by Arcjet Review}

[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/​next@​16.2.6 ⏵ 16.3.1	-2	+40	+1
	npm/​@​arcjet/​sensitive-info-rampart@​1.10.0-rc.0 ⏵ 1.10.0	+1			+3
	npm/​@​anthropic-ai/​claude-agent-sdk@​0.3.233 ⏵ 0.3.234	+1		+1
	npm/​@​ai-sdk/​openai@​3.0.84 ⏵ 3.0.97	+8		+1
	npm/​@​ai-sdk/​react@​3.0.226 ⏵ 3.0.259	+5		+1
	npm/​@​types/​react-dom@​19.2.3 ⏵ 19.2.4	+1		+1	-3
	npm/​@​ai-sdk/​provider-utils@​4.0.38 ⏵ 5.0.27	-3		+1
	npm/​@​types/​react@​19.2.15 ⏵ 19.2.18
	npm/​@​astrojs/​check@​0.9.9 ⏵ 0.9.10				-1
	npm/​eve@​0.31.0 ⏵ 0.38.3	+1		+1	+1
	npm/​@​arcjet/​guard@​1.10.0-rc.0 ⏵ 1.10.0	+3		+1	+1
	npm/​@​fontsource-variable/​figtree@​5.2.10 ⏵ 5.3.0	+1			+6
	npm/​tsx@​4.23.0 ⏵ 4.23.12			+1	-1
	npm/​@​astrojs/​node@​11.1.1 ⏵ 11.1.2	+1		+1	+1
	npm/​@​fontsource/​ibm-plex-mono@​5.2.7 ⏵ 5.3.0			+1	-4
	npm/​react@​19.2.6 ⏵ 19.2.8
	npm/​workflow@​4.8.1 ⏵ 4.8.3	+1			+1
	npm/​firebase-tools@​15.23.0 ⏵ 15.27.0	+10
	npm/​@​tanstack/​react-router@​1.170.17 ⏵ 1.170.29	+17		+4	+1
	npm/​svelte@​5.56.4 ⏵ 5.56.9	+1			+2
	npm/​firebase-functions@​7.2.5 ⏵ 7.3.2	-2		+1	+8
	npm/​@​tanstack/​react-start@​1.168.27 ⏵ 1.168.46			+5	+1
	npm/​astro@​7.2.1 ⏵ 7.2.2			+1
	npm/​isbot@​5.2.0 ⏵ 5.2.1	+1			-3
	npm/​vue-tsc@​3.3.7 ⏵ 3.3.10
	npm/​react-dom@​19.2.6 ⏵ 19.2.8
	npm/​@​fastify/​autoload@​6.4.0 ⏵ 6.5.0				+3
	npm/​react-hook-form@​7.81.0 ⏵ 7.85.0	+1		+1	-1
	npm/​@​nestjs/​common@​11.1.28 ⏵ 11.2.1	+1			+1
	npm/​@​nestjs/​core@​11.1.28 ⏵ 11.2.1	+1			+1
	npm/​svelte-check@​4.7.2 ⏵ 4.7.6	+1			+1
	npm/​@​nestjs/​platform-express@​11.1.28 ⏵ 11.2.1	+1
See 7 more rows in the dashboard

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 vulnerability: npm @fastify/autoload with risk level "medium" Location: Package overview From: examples/fastify/package-lock.json → npm/@fastify/autoload@6.5.0 ℹ Read more on: This package | This alert | Navigating potential vulnerabilities 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: It is advisable to proceed with caution. Engage in a review of the package's security aspects and consider reaching out to the package maintainer for the latest information or patches. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@fastify/autoload@6.5.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 @workflow/core is 78.0% likely risky Notes: High-risk security issue: the code contains a direct eval sink in revive(str) used for v1 compatibility (v1Compat). If attacker-controlled serialized strings can reach this path, it enables arbitrary JavaScript execution (RCE). Other portions (framing/encryption/streaming) look like standard protocol logic, and no clear exfiltration/mining/backdoor behavior is present in the provided fragment. Confidence: 0.78 Severity: 0.86 From: examples/nextjs-ai-agent/package-lock.json → npm/workflow@4.8.3 → npm/@workflow/core@4.8.3 ℹ 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/@workflow/core@4.8.3. 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 @workflow/web is 62.0% likely risky Notes: Overall behavior matches a legitimate workflow orchestration runtime (network I/O, streaming, schema-driven parsing, optional encryption). However, it contains a direct eval-based dynamic execution primitive (revive(str) → (0, eval)(...)) used in a legacy/v1Compat hydration path. If untrusted data can reach the string passed to revive(), this can enable arbitrary code execution. Step execution is also dynamically dispatched based on queue-provided step identifiers, which is security-critical. No explicit overt malware (hardcoded backdoors/cryptomining/exfiltration endpoints) is evident in the provided fragment, but the eval sink makes the module high-risk unless strict trust boundaries ensure revive() input is never attacker-influenced. Confidence: 0.62 Severity: 0.85 From: examples/nextjs-ai-agent/package-lock.json → npm/workflow@4.8.3 → npm/@workflow/web@4.1.19 ℹ 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/@workflow/web@4.1.19. 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 eve is 78.0% likely risky Notes: High security risk: the module includes an explicit JavaScript parsing engine that evaluates attacker-controlled input via eval(), and it also includes YAML tag handling that can dynamically construct functions using the Function(...) constructor. If attacker-controlled front-matter or YAML (with explicit function tags) reaches these code paths, it can lead to arbitrary code execution. Additionally, its file-reading helper can contribute to sensitive file access if paths are attacker-influenced. Confidence: 0.78 Severity: 0.92 From: examples/eve-agent/package-lock.json → npm/eve@0.38.3 ℹ 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/eve@0.38.3. 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 vulnerability: npm firebase-tools with risk level "medium" Location: Package overview From: examples/firebase-functions/package-lock.json → npm/firebase-tools@15.27.0 ℹ Read more on: This package | This alert | Navigating potential vulnerabilities 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: It is advisable to proceed with caution. Engage in a review of the package's security aspects and consider reaching out to the package maintainer for the latest information or patches. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/firebase-tools@15.27.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 firebase-tools is 62.0% likely risky Notes: No direct evidence of stealthy malware (no network/exfiltration/persistence/file tampering observed in this snippet). However, the module is security-sensitive because it can execute an executable specified by process.argv[2] and then executes a derived binary path taken from JSON output without validation/allowlisting. If an attacker can influence argv[2] or the executed tool’s output in the environment, this can become arbitrary command execution in the context of the user. Additionally, unhandled JSON.parse failures introduce reliability/DoS risk, and terminal output derived from child stderr could carry terminal control-sequence risk. Confidence: 0.62 Severity: 0.70 From: examples/firebase-functions/package-lock.json → npm/firebase-tools@15.27.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/firebase-tools@15.27.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 firebase-tools is 65.0% likely risky Notes: No explicit malware or exfiltration behavior is visible in this snippet, but the module is a powerful local execution driver. It can execute arbitrary OS commands from caller-controlled spec fields and can execute dynamically generated JavaScript via node -e based on hook-related inputs. If any upstream supply-chain inputs (spec/bundle/hook or the hook generator) are attacker-controlled, this becomes an effective arbitrary code execution vector with high security risk. Review and harden trust boundaries around spec, genHookScript, and the integrity of hooks_1.BUNDLE_PATH before parsing. Confidence: 0.65 Severity: 0.72 From: examples/firebase-functions/package-lock.json → npm/firebase-tools@15.27.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/firebase-tools@15.27.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 vulnerability: npm next with risk level "medium" Location: Package overview From: examples/nextjs-bot-protection/package-lock.json → npm/next@16.3.1 ℹ Read more on: This package | This alert | Navigating potential vulnerabilities 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: It is advisable to proceed with caution. Engage in a review of the package's security aspects and consider reaching out to the package maintainer for the latest information or patches. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@16.3.1. 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 next is 75.0% likely risky Notes: This code is a manifest loader that can either JSON-parse a manifest or (when useEval is enabled) execute the manifest file contents as JavaScript via vm.runInNewContext. Executing untrusted file content is a significant risk, especially because the VM context is not explicitly hardened and exposes environment-derived data (NEXT_DEPLOYMENT_ID). If an attacker can control or tamper with the manifest file, this module could enable code execution or data exposure; at minimum it substantially increases attack surface compared to pure JSON parsing. Confidence: 0.75 Severity: 0.70 From: examples/nextjs-bot-protection/package-lock.json → npm/next@16.3.1 ℹ 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/next@16.3.1. 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 playwright-core is 70.0% likely risky Notes: No evidence of obfuscated or overtly malicious logic (no persistence, exfiltration, or credential theft) appears in the provided snippet. However, it implements a high-risk supply-chain pattern: it downloads an MSI from a URL provided at runtime and installs it silently via msiexec without any integrity or origin verification. If an attacker can influence $args[0] or the referenced endpoint, this script can facilitate arbitrary MSI payload execution on the host. Confidence: 0.70 Severity: 0.72 From: examples/nextjs/package-lock.json → npm/@playwright/test@1.62.1 → npm/playwright-core@1.62.1 ℹ 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/playwright-core@1.62.1. 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 playwright-core is 76.0% likely risky Notes: This module is a straightforward installer wrapper, but it has a high supply-chain trust boundary risk: it downloads an MSI from a caller-provided URL and silently executes it via msiexec without any integrity/signature validation or URL allowlisting. There is no clear evidence of hidden malware in the visible code, but the execution pattern can enable malicious installer delivery if the URL/contents are compromised or attacker-controlled. Confidence: 0.76 Severity: 0.74 From: examples/nextjs/package-lock.json → npm/@playwright/test@1.62.1 → npm/playwright-core@1.62.1 ℹ 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/playwright-core@1.62.1. 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 playwright-core is 78.0% likely risky Notes: This module is a generic “download-and-silent-install MSI” bootstrapper where the critical control point (the download URL) is fully caller-controlled and the fragment lacks any integrity/signature verification of the downloaded MSI before executing it via msiexec. While there is no explicit backdoor/exfiltration code in the fragment, the combination of (a) arbitrary remote MSI acquisition and (b) silent installer execution makes it a high-risk supply-chain pattern if $args[0] can be influenced or if download provenance cannot be guaranteed externally. Confidence: 0.78 Severity: 0.78 From: examples/nextjs/package-lock.json → npm/@playwright/test@1.62.1 → npm/playwright-core@1.62.1 ℹ 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/playwright-core@1.62.1. 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 seroval is 78.0% likely risky Notes: This module fragment is structurally high risk for supply-chain/security contexts because it generates JavaScript source and includes an explicit (0, eval)(source) deserialization entry point. If an attacker can influence the serialized string passed to deserialize()/compile paths or the plugin set used during reconstruction, it can lead to direct arbitrary code execution. No clear evidence of covert malware (e.g., exfiltration/backdoors) is visible in the provided code; the dominant concern is the intentional code-generation/evaluation design combined with plugin extensibility. Confidence: 0.78 Severity: 0.85 From: examples/tanstack-start/package-lock.json → npm/@tanstack/react-router@1.170.29 → npm/@tanstack/react-start@1.168.46 → npm/seroval@1.6.3 ℹ 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/seroval@1.6.3. 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 seroval is 75.0% likely risky Notes: No clear evidence of overt malware (e.g., network exfiltration, persistence, or credential theft) is visible in this fragment. However, the module is security-critical because deserialization performs direct JavaScript execution via (0, eval)(source) and because a plugin system executes attacker-controlled plugin code when untrusted plugins are used. Therefore, if serialized inputs or plugins are not strictly trusted, the security risk is high and can result in arbitrary code execution. Confidence: 0.75 Severity: 0.87 From: examples/tanstack-start/package-lock.json → npm/@tanstack/react-router@1.170.29 → npm/@tanstack/react-start@1.168.46 → npm/seroval@1.6.3 ℹ 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/seroval@1.6.3. 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 seroval is 84.0% likely risky Notes: This package is fundamentally dangerous when handling untrusted input because it includes an explicit eval-based deserialization entry point (deserialize(source) -> eval). If an attacker can supply or influence the serialized payload, this can lead to arbitrary JavaScript execution (RCE). Additionally, the module reconstructs asynchronous/control-flow primitives and supports non-sandboxed plugins, further expanding execution risk. While the fragment shows no obvious exfiltration or system sabotage code, the eval sink and dynamic reconstruction design make the supply-chain/security risk very high unless inputs and plugins are strictly trusted and controlled. Confidence: 0.84 Severity: 0.94 From: examples/tanstack-start/package-lock.json → npm/@tanstack/react-router@1.170.29 → npm/@tanstack/react-start@1.168.46 → npm/seroval@1.6.3 ℹ 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/seroval@1.6.3. 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 seroval is 82.0% likely risky Notes: No overt covert malware (network/file/process activity) is evident in this fragment; however, the deserialization API includes a direct (0, eval)(source) sink, and the overall design generates executable JavaScript from serialized data and complex constructs. If serialized payloads or plugins are not fully trusted, this creates a high-severity arbitrary code execution risk. Confidence: 0.82 Severity: 0.90 From: examples/tanstack-start/package-lock.json → npm/@tanstack/react-router@1.170.29 → npm/@tanstack/react-start@1.168.46 → npm/seroval@1.6.3 ℹ 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/seroval@1.6.3. 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 tsx is 78.0% likely risky Notes: The primary security issue in this module is direct dynamic code execution: (0, eval) is called on substrings derived from the caller-controlled input during parsing. If parse() is ever invoked with untrusted or partially trusted input, this enables arbitrary JavaScript execution in the consumer environment. The embedded WebAssembly is opaque but also determines what content becomes evaluated and what slices are produced. No explicit exfiltration or filesystem/network activity is visible in this wrapper, but the eval sink makes the overall security posture high-risk. Confidence: 0.78 Severity: 0.90 From: examples/fastify/package-lock.json → npm/tsx@4.23.12 ℹ 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/tsx@4.23.12. 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 tsx is 62.0% likely risky Notes: This module is a runtime execution hook that patches Node’s REPL eval to transform user-entered code with esbuild (including TS parsing) and rewrites require to global.require in the transformed output before executing it via the original eval. While there is no direct evidence of network exfiltration or credential theft within this snippet, the pattern is strongly suspicious because it expands execution capabilities and alters module-loading semantics at runtime, with silent error suppression reducing observability. Confidence: 0.62 Severity: 0.70 From: examples/fastify/package-lock.json → npm/tsx@4.23.12 ℹ 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/tsx@4.23.12. 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 @smithy/core is 65.0% likely to have a medium risk anomaly Notes: The code implements a conventional, well-structured event-stream unmarshalling pipeline with explicit handling for error, exception, and event message types. The primary security considerations are: potential exposure of header/body content through thrown errors, reliance on the deserializer contract (notably the $unknown flag), and ensuring that downstream consumers appropriately trust the deserialized payloads. In a supply-chain context, ensure that eventStreamCodec, deserializer implementations, and error handling are trusted and audited to avoid leaking sensitive metadata, and consider sanitizing error messages in production. Confidence: 0.65 Severity: 0.60 From: examples/nextjs-ai-agent/package-lock.json → npm/workflow@4.8.3 → npm/@smithy/core@3.33.3 ℹ 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/@smithy/core@3.33.3. 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 @tanstack/react-router is 72.0% likely to have a medium risk anomaly Notes: Functionally, this is an SSR-only “inject once” script helper. It is not inherently malicious, but it is a powerful code-injection sink: whatever string is passed as children becomes executable JavaScript in the client via dangerouslySetInnerHTML inside a <script> tag. Security impact therefore depends entirely on whether children is strictly trusted (e.g., developer-authored constants) versus attacker-influenced. No network/exfiltration/backdoor behavior is present in the provided fragment. Confidence: 0.72 Severity: 0.56 From: examples/tanstack-start/package-lock.json → npm/@tanstack/react-router@1.170.29 ℹ 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/@tanstack/react-router@1.170.29. 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 @tanstack/start-plugin-core is 62.0% likely to have a medium risk anomaly Notes: No clear indicators of classic malware (exfiltration, reverse shells, credential theft, or code execution) are present in this module. The dominant supply-chain/security risk is build-time: crawl targets and output filenames are influenced by link-derived hrefs and auto-discovered global data without the same strict validation applied to initial page paths. Combined with computed filepath creation (path.join(outputDir, filename)) and lack of explicit enforcement that the final resolved path stays within outputDir, this creates a plausible directory traversal / arbitrary file write risk if href/page/path normalization utilities do not fully eliminate traversal sequences. Additionally, writing fetched HTML verbatim can propagate upstream HTML content into the generated site. Confidence: 0.62 Severity: 0.58 From: examples/tanstack-start/package-lock.json → npm/@tanstack/react-start@1.168.46 → npm/@tanstack/start-plugin-core@1.171.36 ℹ 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/@tanstack/start-plugin-core@1.171.36. 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.
See 51 more rows in the dashboard

View full report