Skip to content

chore(deps): bump the npm_and_yarn group across 5 directories with 2 …

1214440
Select commit
Loading
Failed to load commit list.
Closed

chore(deps): bump the npm_and_yarn group across 5 directories with 2 updates #184

chore(deps): bump the npm_and_yarn group across 5 directories with 2 …
1214440
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts failed May 25, 2026 in 37s

Pull Request #184 Alerts: Complete with warnings

Report Status Message
PR #184 Alerts ⚠️ Found 2 project alerts

Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.

Details

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 Medium
Potential vulnerability: npm @sveltejs/kit with risk level "medium"

Location: Package overview

From: examples/sveltekit/package-lock.jsonnpm/@sveltejs/kit@2.61.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/@sveltejs/kit@2.61.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.

Warn Low
Publisher changed: npm body-parser is now published by jonchurch instead of ulisesgascon

New Author: jonchurch

Previous Author: ulisesgascon

From: examples/react-router/package-lock.jsonnpm/firebase-functions@7.2.5npm/@react-router/serve@7.14.1npm/firebase-tools@15.15.0npm/body-parser@1.20.5

ℹ Read more on: This package | This alert | What is new author?

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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/body-parser@1.20.5. 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