socket-security[bot]
commented
3 months ago New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Package | New capabilities | Transitives | Size | Publisher |
|---|
Closed dependabot[bot] closed 3 months ago
socket-security[bot]
commented
3 months ago New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Package | New capabilities | Transitives | Size | Publisher |
|---|
socket-security[bot]
commented
3 months ago 👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎
This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.
Ignoring: npm/p-try@2.2.0, npm/path-exists@4.0.0, npm/path-type@4.0.0, npm/picomatch@2.3.1, npm/pify@4.0.1, npm/proto-list@1.2.4, npm/pseudomap@1.0.2, npm/queue-microtask@1.2.3, npm/reusify@1.0.4, npm/shebang-regex@1.0.0, npm/signal-exit@3.0.7, npm/slash@3.0.0, npm/sprintf-js@1.0.3, npm/strip-bom@3.0.0, npm/strip-json-comments@2.0.1, npm/undici-types@5.26.5, npm/universalify@0.1.2, npm/yallist@2.1.2
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
lishaduck
commented
3 months ago @SocketSecurity ignore-all
Bumps the build group with 2 updates: turbo and vite.
Updates
turbofrom 2.0.6 to 2.0.9Release notes
Sourced from turbo's releases.
... (truncated)
Commits
ea74070publish 2.0.9 to registryf00b73dfeat(examples): bump turbo for svelte (#8796)925ed6ffeat(turborepo): turbo ls with filter (#8779)5a68e3afeature(turborepo): fancy package.json errors (#8299)b51e9e4release(turborepo): 2.0.8 (#8795)3c2991cfeat(turbo): add VERCEL to pass through (#8794)332589afix watcher bug with file creation (#8785)c5ae6fbchore(ci): JS tests don't need to setup rust and capnproto (#8787)8de0996chore(ci): rm unused input to custom action (#8789)f9bf670chore(ci): run JS package tests on node 18 (#8730)Updates
vitefrom 5.3.3 to 5.3.4Changelog
Sourced from vite's changelog.
Commits
4e57a97release: v5.3.41465b20fix(css): include.css?urlin assets field of manifest (#17623)c4a2227refactor: replace includes with logical operations (#17620)d8a5d70chore: add callback to http-proxy.d.ts jsdoc (#17646)4be96b4fix(build): skip preload treeshaking for nested braces (#17687)b723a75fix: update Terser type definitions (fix #17668) (#17669)07bc489fix(worker): nested inlined worker always fallbacked to data URI worker inste...Dependabot 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