Skip to content

Bump the npm_and_yarn group across 2 directories with 12 updates #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump the npm_and_yarn group across 2 directories with 12 updates #11

wants to merge 1 commit into from

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Aug 28, 2025

Bumps the npm_and_yarn group with 1 update in the /backend directory: multer.
Bumps the npm_and_yarn group with 11 updates in the /frontend directory:

Package From To
esbuild 0.18.20 0.25.9
vite 5.4.19 7.1.3
vite-plugin-pwa 0.17.5 1.0.3
vitest 0.34.6 3.2.4
@vitest/ui 0.34.7 3.2.4
@storybook/addon-essentials 7.6.20 8.6.14
@storybook/addon-onboarding 1.0.11 9.1.3
@storybook/blocks 7.6.20 8.6.14
@storybook/react 7.6.20 9.1.3
@storybook/react-vite 7.6.20 9.1.3
storybook 7.6.20 9.1.3

Updates multer from 1.4.5-lts.2 to 2.0.2

Release notes

Sourced from multer's releases.

v2.0.2

Important

Full Changelog: expressjs/multer@v2.0.1...v2.0.2

v2.0.1

Important

What's Changed

New Contributors

... (truncated)

Changelog

Sourced from multer's changelog.

2.0.2

2.0.1

2.0.0

Commits
Maintainer changes

This version was pushed to npm by ulisesgascon, a new releaser for multer since your current version.


Updates esbuild from 0.18.20 to 0.25.9

Release notes

Sourced from esbuild's releases.

v0.25.9

  • Better support building projects that use Yarn on Windows (#3131, #3663)

    With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

    1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
    2. Some developers put their projects on the D: drive
    3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
    4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
    5. I didn't have access to a Windows machine for testing this edge case

    Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.

  • Preserve parentheses around function expressions (#4252)

    The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

    Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:

    // Original code
const fn0 = () => 0
const fn1 = (() => 1)
console.log(fn0, function() { return fn1() }())
// Old output
const fn0 = () => 0;
const fn1 = () => 1;
console.log(fn0, function() {
return fn1();
}());
// New output
const fn0 = () => 0;
const fn1 = (() => 1);
console.log(fn0, (function() {
return fn1();
})());

    Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.

  • Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

v0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

  • Fix TypeScript-specific class transform edge case (#3559)

    The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

    // Original code
class Foo extends Bar {
  #private = 1;
  public: any;
  constructor() {
    super();
  }
}
// Old output (with esbuild v0.19.9)
class Foo extends Bar {
constructor() {
super();
this.#private = 1;
}
#private;
}
// Old output (with esbuild v0.19.10)
class Foo extends Bar {
constructor() {
this.#private = 1;
super();
}
#private;
}
// New output
class Foo extends Bar {
#private = 1;
constructor() {
super();
}
}

  • Minifier: allow reording a primitive past a side-effect (#3568)

    The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (truncated)

Commits

Updates vite from 5.4.19 to 7.1.3

Release notes

Sourced from vite's releases.

v7.1.3

Please refer to CHANGELOG.md for details.

v7.1.2

Please refer to CHANGELOG.md for details.

v7.1.1

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

v7.1.0

Please refer to CHANGELOG.md for details.

v7.1.0-beta.1

Please refer to CHANGELOG.md for details.

v7.1.0-beta.0

Please refer to CHANGELOG.md for details.

v7.0.6

Please refer to CHANGELOG.md for details.

v7.0.5

Please refer to CHANGELOG.md for details.

v7.0.4

Please refer to CHANGELOG.md for details.

v7.0.3

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

v7.0.2

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

v7.0.1

Please refer to CHANGELOG.md for details.

... (truncated)

Changelog

Sourced from vite's changelog.

7.1.3 (2025-08-19)

Features

  • cli: add Node.js version warning for unsupported versions (#20638) (a1be1bf)
  • generate code frame for parse errors thrown by terser (#20642) (a9ba017)
  • support long lines in generateCodeFrame (#20640) (1559577)

Bug Fixes

  • deps: update all non-major dependencies (#20634) (4851cab)
  • optimizer: incorrect incompatible error (#20439) (446fe83)
  • support multiline new URL(..., import.meta.url) expressions (#20644) (9ccf142)

Performance Improvements

Miscellaneous Chores

Code Refactoring

Tests

7.1.2 (2025-08-12)

Bug Fixes

  • client: add [vite] prefixes to debug logs (#20595) (7cdef61)
  • config: make debugger work with bundle loader (#20573) (c583927)
  • deps: update all non-major dependencies (#20587) (20d4817)
  • don't consider ids with npm: prefix as a built-in module (#20558) (ab33803)
  • hmr: watch non-inlined assets referenced by CSS (#20581) (b7d494b)
  • module-runner: prevent crash when sourceMappingURL pattern appears in string literals (#20554) (2770478)

Miscellaneous Chores

  • deps: migrate to @jridgewell/remapping from @ampproject/remapping (#20577) (0a6048a)
  • deps: update rolldown-related dependencies (#20586) (77632c5)

7.1.1 (2025-08-08)

Bug Fixes

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vite since your current version.


Updates vite-plugin-pwa from 0.17.5 to 1.0.3

Release notes

Sourced from vite-plugin-pwa's releases.

v1.0.3

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v1.0.2

   🚀 Features

    View changes on GitHub

v1.0.1

   🐞 Bug Fixes

    View changes on GitHub

v1.0.0

   🚨 Breaking Changes

   🐞 Bug Fixes

    View changes on GitHub

v0.21.2

   🐞 Bug Fixes

    View changes on GitHub

v0.21.1

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

Updates vitest from 0.34.6 to 3.2.4

Release notes

Sourced from vitest's releases.

v3.2.4

   🐞 Bug Fixes

    View changes on GitHub

v3.2.3

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v3.2.2

... (truncated)

Commits
  • c666d14 chore: release v3.2.4
  • 8a18c8e fix(cli): throw error when --shard x/\<count> exceeds count of test files (#...
  • 8abd7cc chore(deps): update tinypool (#8174)
  • 93f3200 fix(deps): update all non-major dependencies (#8123)
  • 0c3be6f fix(coverage): ignore SCSS in browser mode (#8161)
  • 790bc31 chore: update deprecation notice for globs (#8148)
  • c0eae7d chore: update deprecated workspace file log (#8118)
  • 14dc072 fix(pool): auto-adjust minWorkers when only maxWorkers specified (#8110)
  • 85dc019 fix(cli): use absolute path environment on Windows (#8105)
  • 27df68a fix(reporter): task.meta should be available in custom reporter's errors (#...
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by vitestbot, a new releaser for vitest since your current version.


Updates @vitest/ui from 0.34.7 to 3.2.4

Release notes

Sourced from @​vitest/ui's releases.

v3.2.4

   🐞 Bug Fixes

    View changes on GitHub

v3.2.3

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v3.2.2

... (truncated)

Commits
  • c666d14 chore: release v3.2.4
  • 93f3200 fix(deps): update all non-major dependencies (#8123)
  • b87ee3e chore: release v3.2.3
  • c69be1f feat(ui): show test annotations and metadata in the test report tab (#8093)
  • 7ddcd33 chore: release v3.2.2
  • f858f3b chore: release v3.2.1
  • 59200ae chore: release v3.2.0
  • cce98d3 chore(deps): update all non-major dependencies (#8067)
  • b03f209 feat: annotation API (#7953)
  • 3bdf05d fix: ensure errors keep their message and stack after toJSON serialisation ...
  • Additional commits viewable in

@dependabot
Bump the npm_and_yarn group across 2 directories with 12 updates
4e5709f 
Bumps the npm_and_yarn group with 1 update in the /backend directory: [multer](https://github.com/expressjs/multer).
Bumps the npm_and_yarn group with 11 updates in the /frontend directory:

| Package | From | To |
| --- | --- | --- |
| [esbuild](https://github.com/evanw/esbuild) | `0.18.20` | `0.25.9` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `5.4.19` | `7.1.3` |
| [vite-plugin-pwa](https://github.com/vite-pwa/vite-plugin-pwa) | `0.17.5` | `1.0.3` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `0.34.6` | `3.2.4` |
| [@vitest/ui](https://github.com/vitest-dev/vitest/tree/HEAD/packages/ui) | `0.34.7` | `3.2.4` |
| [@storybook/addon-essentials](https://github.com/storybookjs/storybook/tree/HEAD/code/addons/essentials) | `7.6.20` | `8.6.14` |
| [@storybook/addon-onboarding](https://github.com/storybookjs/storybook/tree/HEAD/code/addons/onboarding) | `1.0.11` | `9.1.3` |
| [@storybook/blocks](https://github.com/storybookjs/storybook/tree/HEAD/code/lib/blocks) | `7.6.20` | `8.6.14` |
| [@storybook/react](https://github.com/storybookjs/storybook/tree/HEAD/code/renderers/react) | `7.6.20` | `9.1.3` |
| [@storybook/react-vite](https://github.com/storybookjs/storybook/tree/HEAD/code/frameworks/react-vite) | `7.6.20` | `9.1.3` |
| [storybook](https://github.com/storybookjs/storybook/tree/HEAD/code/core) | `7.6.20` | `9.1.3` |



Updates `multer` from 1.4.5-lts.2 to 2.0.2
- [Release notes](https://github.com/expressjs/multer/releases)
- [Changelog](https://github.com/expressjs/multer/blob/main/CHANGELOG.md)
- [Commits](expressjs/multer@v1.4.5-lts.2...v2.0.2)

Updates `esbuild` from 0.18.20 to 0.25.9
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2023.md)
- [Commits](evanw/esbuild@v0.18.20...v0.25.9)

Updates `vite` from 5.4.19 to 7.1.3
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v7.1.3/packages/vite)

Updates `vite-plugin-pwa` from 0.17.5 to 1.0.3
- [Release notes](https://github.com/vite-pwa/vite-plugin-pwa/releases)
- [Commits](vite-pwa/vite-plugin-pwa@v0.17.5...v1.0.3)

Updates `vitest` from 0.34.6 to 3.2.4
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v3.2.4/packages/vitest)

Updates `@vitest/ui` from 0.34.7 to 3.2.4
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v3.2.4/packages/ui)

Updates `@storybook/addon-essentials` from 7.6.20 to 8.6.14
- [Release notes](https://github.com/storybookjs/storybook/releases)
- [Changelog](https://github.com/storybookjs/storybook/blob/v8.6.14/CHANGELOG.md)
- [Commits](https://github.com/storybookjs/storybook/commits/v8.6.14/code/addons/essentials)

Updates `@storybook/addon-onboarding` from 1.0.11 to 9.1.3
- [Release notes](https://github.com/storybookjs/storybook/releases)
- [Changelog](https://github.com/storybookjs/storybook/blob/next/code/addons/onboarding/CHANGELOG.md)
- [Commits](https://github.com/storybookjs/storybook/commits/v9.1.3/code/addons/onboarding)

Updates `@storybook/blocks` from 7.6.20 to 8.6.14
- [Release notes](https://github.com/storybookjs/storybook/releases)
- [Changelog](https://github.com/storybookjs/storybook/blob/v8.6.14/CHANGELOG.md)
- [Commits](https://github.com/storybookjs/storybook/commits/v8.6.14/code/lib/blocks)

Updates `@storybook/react` from 7.6.20 to 9.1.3
- [Release notes](https://github.com/storybookjs/storybook/releases)
- [Changelog](https://github.com/storybookjs/storybook/blob/next/CHANGELOG.md)
- [Commits](https://github.com/storybookjs/storybook/commits/v9.1.3/code/renderers/react)

Updates `@storybook/react-vite` from 7.6.20 to 9.1.3
- [Release notes](https://github.com/storybookjs/storybook/releases)
- [Changelog](https://github.com/storybookjs/storybook/blob/next/CHANGELOG.md)
- [Commits](https://github.com/storybookjs/storybook/commits/v9.1.3/code/frameworks/react-vite)

Updates `storybook` from 7.6.20 to 9.1.3
- [Release notes](https://github.com/storybookjs/storybook/releases)
- [Changelog](https://github.com/storybookjs/storybook/blob/next/CHANGELOG.md)
- [Commits](https://github.com/storybookjs/storybook/commits/v9.1.3/code/core)

---
updated-dependencies:
- dependency-name: multer
  dependency-version: 2.0.2
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.9
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: vite
  dependency-version: 7.1.3
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: vite-plugin-pwa
  dependency-version: 1.0.3
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: vitest
  dependency-version: 3.2.4
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: "@vitest/ui"
  dependency-version: 3.2.4
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: "@storybook/addon-essentials"
  dependency-version: 8.6.14
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: "@storybook/addon-onboarding"
  dependency-version: 9.1.3
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: "@storybook/blocks"
  dependency-version: 8.6.14
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: "@storybook/react"
  dependency-version: 9.1.3
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: "@storybook/react-vite"
  dependency-version: 9.1.3
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: storybook
  dependency-version: 9.1.3
  dependency-type: direct:development
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 28, 2025
@code-genius-code-coverage
Copy link

code-genius-code-coverage bot commented Aug 28, 2025

The files' contents are under analysis for test generation.

@semanticdiff-com
Copy link

semanticdiff-com bot commented Aug 28, 2025 •
edited
Loading

Review changes with  SemanticDiff

Changed Files
File Status
  backend/package-lock.json  19% smaller
  backend/package.json  0% smaller
  frontend/package-lock.json Unsupported file format
  frontend/package.json  0% smaller

@secure-code-warrior-for-github
Copy link

secure-code-warrior-for-github bot commented Aug 28, 2025

Micro-Learning Topic: Directory traversal (Detected by phrase)

Matched on "directory traversal"

What is this? (2min video)

Path traversal vulnerabilities occur when inputs that have not been sufficiently validated or sanitised are used to build directory or file paths. If an attacker can influence the path being accessed by the server, they may be able to gain unauthorised access to files or even execute arbitrary code on the server (when coupled with file upload functionality).

Try a challenge in Secure Code Warrior

Helpful references
  • OWASP Input Validation Cheat Sheet - This cheatsheet is focused on providing clear, simple, actionable guidance for preventing injection and input validation flaws in your applications, including defence against path traversal.
  • OWASP Path Traversal - OWASP community page with comprehensive information about path traversal, and links to various OWASP resources to help detect or prevent it.

@gitnotebooks
Copy link

gitnotebooks bot commented Aug 28, 2025

Review these changes at https://app.gitnotebooks.com/OneFineStarstuff/OneFineStarstuff.github.io/pull/11

reviewabot[bot]
reviewabot bot approved these changes Aug 28, 2025
View reviewed changes
Copy link

@reviewabot reviewabot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could not review PR. Too many requests in the last 5 minutes.
Max 1 pr 5 minutes. Last review was in OneFineStarstuff/OneFineStarstuff.github.io at Thu, 28 Aug 2025 16:12:26 GMT.
Next review is available in approx 2 minutes.
Upgrade to a premium Reviewabot plan or contact us at [email protected] to request an exemption.

@coderabbitai
Copy link

coderabbitai bot commented Aug 28, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbit review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbit in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbit in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbit gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbit read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbit help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbit ignore or @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbit summary or @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbit or @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@gstraccini gstraccini bot added the 🤖 bot label Aug 28, 2025
@socket-security
Copy link

socket-security bot commented Aug 28, 2025

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

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Addedcrypto@​1.0.11001003975100
Addedjest@​29.7.01001006697100
Addedexpress-brute@​1.0.1919610076100
Addedpassport-local@​1.0.01001009076100
Addedhpp@​0.2.310010010076100
Addedeslint-config-node@​4.1.01001009376100
Addedexpress-mongo-sanitize@​2.2.010010010076100
Addedpassport-jwt@​4.0.110010010077100
Addedpassport@​0.7.010010010077100
Addedxss@​1.0.1510010010077100
Addedjoi@​17.13.31001007790100
Addedhusky@​8.0.31001007778100
Updated@​types/​node@​24.3.0 ⏵ 20.19.111001008096100
Addedbcryptjs@​2.4.31001001008080
Addedcors@​2.8.510010010080100
Addedjsonwebtoken@​9.0.29910010081100
Addedsocket.io@​4.8.19910010081100
Addedhelmet@​7.2.010010010081100
Addednodemon@​3.1.109710010081100
Addedexpress-validator@​7.2.11001008182100
Addedsharp@​0.32.6981001008670
Addedwinston-daily-rotate-file@​4.7.110010010082100
Addedmorgan@​1.10.19910010082100
Addeddompurify@​3.2.61001001008390
Addedexpress-session@​1.18.29910010083100
Addedpg-pool@​3.10.110010010083100
Addeduuid@​9.0.110010010084100
Addedpg@​8.16.3991009984100
Addedwinston@​3.17.09910010085100
Addedconnect-redis@​7.1.110010010086100
Addedexpress-rate-limit@​7.5.110010010086100
Addednodemailer@​6.10.1981009786100
See 9 more rows in the dashboard

View full report

@socket-security
Copy link

socket-security bot commented Aug 28, 2025

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Critical
[email protected] has a Critical CVE.

CVE: GHSA-cf4h-3jhx-xvhq Arbitrary Code Execution in underscore (CRITICAL)

Affected versions: >= 1.3.2 < 1.12.1

Patched version: 1.12.1

From: backend/package-lock.json → npm/[email protected] → npm/[email protected]

ℹ Read more on: This package | This alert | What is a critical CVE?

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 [email protected].

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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

@secure-code-warrior-for-github
Copy link

secure-code-warrior-for-github bot commented Aug 28, 2025

Micro-Learning Topic: Cross-site scripting (Detected by phrase)

Matched on "xss"

Cross-site scripting vulnerabilities occur when unescaped input is rendered into a page displayed to the user. When HTML or script is included in the input, it will be processed by a user's browser as HTML or script and can alter the appearance of the page or execute malicious scripts in their user context.

Try a challenge in Secure Code Warrior

Helpful references

@difflens
Copy link

difflens bot commented Aug 28, 2025

View changes in DiffLens

github-actions[bot]
github-actions bot reviewed Aug 28, 2025
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Message that will be displayed on users' first pull request

@netlify
Copy link

netlify bot commented Aug 28, 2025 •
edited
Loading

❌ Deploy Preview for onefinestarstuff failed.

Name Link
🔨 Latest commit 4e5709f
🔍 Latest deploy log https://app.netlify.com/projects/onefinestarstuff/deploys/68b0808ac36d5f0008103b7e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@github-actions github-actions[bot] github-actions[bot] left review comments

@gstraccini gstraccini[bot] gstraccini[bot] approved these changes

+1 more reviewer

@reviewabot reviewabot[bot] reviewabot[bot] approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@OneFineStarstuff OneFineStarstuff

Labels

☑️ auto-merge 🤖 bot dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code size/S

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@OneFineStarstuff