Closed dependabot[bot] closed 3 weeks ago
Merging to main
in this repository is managed by Trunk.
/trunk merge
below.New dependencies detected. Learn more about Socket for GitHub ↗︎
Package | New capabilities | Transitives | Size | Publisher |
---|---|---|---|---|
npm/@clerk/nextjs@5.7.2 | Transitive: environment, network | +18 |
6.05 MB | nikosdouvlis |
npm/@types/react-dom@18.3.1 | None | 0 |
0 B | |
npm/eslint-config-next@14.2.15 | unsafe Transitive: environment, filesystem | +60 |
7.11 MB | vercel-release-bot |
npm/next@14.2.15 | environment, filesystem, network, shell, unsafe | +11 |
448 MB | vercel-release-bot |
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎
To accept the risk, merge this PR and you will not be notified again.
Alert | Package | Note | Source | CI |
---|---|---|---|---|
New author | npm/cookie@0.7.0 |
| 🚫 | |
Unstable ownership | npm/cookie@0.7.0 |
| 🚫 |
A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
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.
A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.
Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.
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 [AT] socket [DOT] dev.
If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.
To ignore an alert, reply with a comment starting with @SocketSecurity ignore
followed by a space separated list of ecosystem/package-name@version
specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0
or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/cookie@0.7.0
Superseded by #1929.
Bumps the dependencies group with 4 updates in the /examples/nextjs-14-clerk-rl directory: @clerk/nextjs, next, @types/react-dom and eslint-config-next.
Updates
@clerk/nextjs
from 5.7.1 to 5.7.2Release notes
Sourced from
@clerk/nextjs
's releases.Changelog
Sourced from
@clerk/nextjs
's changelog.Commits
d724a36
ci(repo): Version packages (#4307)0d56455
fix(nextjs): do not build test file declarations (#4286)3b6d510
chore(repo): Node 20 / attw change (#4283)Updates
next
from 14.2.14 to 14.2.15Release notes
Sourced from next's releases.
Commits
737c29e
v14.2.151c8234e
backport: [i18n] Routing fix #70761 (#70976)bb3f580
fix: Do not omit alt on getImgProps return type, ImgProps (#70818)cb8113b
fix(next/image): handle undefinedimages.localPatterns
config in `images-ma...9c1191a
fix missing helpers innext-test-utils.ts
0de4183
fix linte03c4ff
feat(next/image): addimages.localPatterns
config (#70802)540ea2d
backport: support breadcrumb style catch-all parallel routes (#65063) (#70794)0d0448b
Fix client reference access causing metadata missing (#70732) (#70788)381d1f9
feat(next/image): add support fordecoding
prop (#70678)Updates
@types/react-dom
from 18.3.0 to 18.3.1Commits
Updates
eslint-config-next
from 14.2.14 to 14.2.15Release notes
Sourced from eslint-config-next's releases.
Commits
737c29e
v14.2.15Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show