[Snyk] Fix for 1 vulnerabilities

[naiba4]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json
  • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	591/1000 Why? Recently disclosed, Has a fix available, CVSS 6.1	Open Redirect SNYK-JS-EXPRESS-6474509	Yes	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: @bull-board/express

The new version differs by 220 commits.

• cda599b Release 5.10.2
• 8a27924 fix: remove the strict need for express deps, closes #656
• a13e4d5 add an example with csrf token enabled
• cf1a136 Release 5.10.1
• 3014f47 fix: align en locale lang to be full specified (en-US)
• e06f3b5 add locale pt-BR (feat: added docker-compose.log.yml for log viewer chrisleekr/binance-trading-bot#654)
• ea75f2e Release 5.10.0
• de5350d feat: add bundle-analyzer
• 396bf70 fix: reduce bundle size
• 615daa4 feat: add translation ability, Docker Proxy Support (Outgoing connections) chrisleekr/binance-trading-bot#653
• 3d9ee8f chore(deps-dev): bump axios from 0.26.1 to 1.6.0 (Notional value is less than the minimum notional value. Do not place an order for the grid trade #1. chrisleekr/binance-trading-bot#644)
• 03afb90 Release 5.9.2
• b5ace07 Update QueueAdapterOptions typing (#652)
• 37a618f upgrade-express-ex: upgrade express example (ImportError: cannot import name 'url_quote' from 'werkzeug.urls' (/usr/local/lib/python3.9/site-packages/werkzeug/urls.py) chrisleekr/binance-trading-bot#648)
• 9ce2f63 Release 5.9.1
• 7ce08ab Update readme
• 39a1333 Update README.md (feat: update deps, conf and fix test chrisleekr/binance-trading-bot#638)
• 8f30a87 chore(deps): bump @ babel/traverse from 7.22.15 to 7.23.2 (Can you create a video showing your installations? chrisleekr/binance-trading-bot#637)
• 3e45bb5 chore(deps-dev): bump @ babel/traverse in /examples/with-nestjs (Stuck on Failed to load account information, how it`s fix chrisleekr/binance-trading-bot#636)
• 04af55b chore(deps): bump @ babel/traverse in /examples/with-nestjs-module (Buy order stop price is higher than current buy limit price, cancel current buy order chrisleekr/binance-trading-bot#635)
• 6109d30 Release 5.9.0
• 6a4b2ce feat: add new statuses to overview page
• 816fe76 feat: add overlay page to readme
• 8e5fe74 feat: Improve progress bar layout

See the full diff

Package name: express

The new version differs by 77 commits.

• b28db2c 4.19.2
• 0b74695 Improved fix for open redirect allow list bypass
• 4f0f6cc 4.19.1
• a003cfa Allow passing non-strings to res.location with new encoding handling checks fixes #5554 #5555
• a1fa90f fixed un-edited version in history.md for 4.19.0
• 11f2b1d build: fix build due to inconsistent supertest behavior in older versions
• 084e365 4.19.0
• 0867302 Prevent open redirect allow list bypass due to encodeurl
• 567c9c6 Add note on how to update docs for new release (#5541)
• 69a4cf2 deps: [email protected]
• 4ee853e docs: loosen TC activity rules
• 414854b docs: nominating @ wesleytodd to be project captian
• 06c6b88 docs: update release date
• 1b51eda 4.18.3
• b625132 build: pin Node 21.x to minor
• e3eca80 build: pin Node 21.x to minor
• 23b44b3 build: support Node.js 21.6.2
• b9fea12 build: support Node.js 21.x in appveyor
• c259c34 build: support Node.js 21.x
• fdeb1d3 build: support Node.js 20.x in appveyor
• 734b281 build: support Node.js 20.x
• 0e3ab6e examples: improve view count in cookie-sessions
• 59af63a build: [email protected]
• e720c5a docs: add documentation for benchmarks

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Open Redirect

[cloudflare-workers-and-pages]

Deploying binance-trading-bot with    Cloudflare Pages

Latest commit:	483a032
Status:	🚫  Build failed.

View logs

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[guardrails]

⚠️ We detected 2 security issues in this pull request:

Vulnerable Libraries (2)

Severity	Details
High	pkg:npm/@bull-board/[email protected] upgrade to: > 5.10.2
High	pkg:npm/[email protected] upgrade to: > 4.19.2

More info on how to fix Vulnerable Libraries in JavaScript.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@bull-board/[email protected]	None	0	11.5 kB	felixmosh
npm/@bull-board/[email protected]	None	0	2.56 MB	felixmosh
npm/[email protected]	network	0	60.8 kB	dougwilson
npm/[email protected]	None	0	10.5 kB	dougwilson
npm/[email protected]	None	0	23.7 kB	dougwilson
npm/[email protected]	environment, filesystem, network	0	215 kB	wesleytodd
npm/[email protected]	network, unsafe	0	25.8 kB	dougwilson

🚮 Removed packages: npm/@bull-board/[email protected], npm/@bull-board/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 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
Unstable ownership	npm/[email protected]	Author: wesleytodd	package-lock.json package.json

View full report↗︎

Next steps

What is unstable ownership?

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 deeper look at the dependency

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.

Remove the package

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.

Mark a package as acceptable risk

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]

[pull-request-quantifier-deprecated]

This PR has 4 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +2 -2
Percentile : 1.6%

Total files changed: 1

Change summary by file extension:
.json : +2 -2

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.