chore(deps): bump express-rate-limit from 7.5.1 to 8.5.2

[dependabot]

Bumps express-rate-limit from 7.5.1 to 8.5.2.

Release notes

Sourced from express-rate-limit's releases.

v8.5.2

You can view the changelog here.

v8.5.1

You can view the changelog here.

v8.5.0

You can view the changelog here.

v8.4.1

You can view the changelog here.

v8.4.0

You can view the changelog here.

v8.3.2

You can view the changelog here.

v8.3.1

You can view the changelog here.

v8.3.0

You can view the changelog here.

v8.2.1

You can view the changelog here.

v8.2.0

You can view the changelog here.

v8.1.0

You can view the changelog here.

v8.0.1

You can view the changelog here.

v8.0.0

You can view the changelog here.

Commits

• 9774693 8.5.2
• 0e94cc0 v8.5.2 changelog
• 9a583c5 feat: simplify IPv6 key generation (#633)
• 4f4b3fb chore(deps-dev): bump lint-staged from 16.4.0 to 17.0.4 (#632)
• 3c1d6c5 chore(deps-dev): bump the development-dependencies group with 7 updates (#631)
• 18884b6 chore(deps): bump basic-ftp from 5.2.0 to 5.3.1 (#630)
• dacc980 chore(deps): bump handlebars from 4.7.8 to 4.7.9 (#629)
• 486d0c6 chore(deps): bump follow-redirects from 1.15.11 to 1.16.0 (#627)
• 50cc3f6 8.5.1
• 92c8e3e chore: bump ip-address library to latest (#626)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for express-rate-limit since your current version.

Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​mjml@​4.7.4
	@​types/​damerau-levenshtein@​1.0.2
	@​types/​subset-font@​1.4.3
	@​types/​uuid@​10.0.0
	@​types/​readline-sync@​1.4.8
	@​tanstack/​solid-hotkeys-devtools@​0.6.6
	@​tanstack/​solid-query-devtools@​5.100.3
	@​types/​throttle-debounce@​5.0.2
	@​tanstack/​solid-db@​0.2.21
	@​types/​express@​5.0.3
	@​types/​object-hash@​3.0.6
	@​types/​cron@​1.7.3
	@​types/​supertest@​6.0.3
	@​types/​ua-parser-js@​0.7.36
	@​types/​bcrypt@​5.0.2
	@​sentry/​browser@​10.44.0
	@​types/​swagger-stats@​0.95.11
	@​tanstack/​solid-table@​8.21.3
	@​types/​howler@​2.2.7
	@​tanstack/​query-db-collection@​1.0.38
	@​types/​mustache@​4.2.2
	@​types/​chartjs-plugin-trendline@​1.0.1
	@​tanstack/​eslint-plugin-query@​5.100.3
	balloon-css@​1.2.0
	@​storybook/​addon-vitest@​10.2.16
	@​types/​ioredis@​4.28.10
	@​types/​nodemailer@​6.4.15
	@​redocly/​cli@​2.24.1
	@​tanstack/​solid-devtools@​0.8.2
	@​tanstack/​solid-hotkeys@​0.10.0
	@​storybook/​addon-a11y@​10.2.16
	@​oxlint/​plugins@​1.43.0
	@​vitest/​browser@​4.1.6
See 27 more rows in the dashboard

View full report

[socket-security]

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 CVE: Vitest browser mode serves unsanitized otelCarrier query parameter as inline script in npm @vitest/browser CVE: GHSA-2h32-95rg-cppp Vitest browser mode serves unsanitized otelCarrier query parameter as inline script (CRITICAL) Affected versions: >= 4.0.17 < 4.1.6; >= 5.0.0-beta.0 < 5.0.0-beta.3 Patched version: 4.1.6 From: pnpm-lock.yaml → npm/@vitest/browser-playwright@4.0.18 → npm/@vitest/browser@4.0.18 ℹ 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 support@socket.dev. 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/@vitest/browser@4.0.18. 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