Skip to content

Update dependency recharts to v2.15.4#8

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/recharts-2.x
Open

Update dependency recharts to v2.15.4#8
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/recharts-2.x

Conversation

@renovate

@renovate renovate Bot commented Aug 8, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
recharts 2.15.02.15.4 age confidence

Release Notes

recharts/recharts (recharts)

v2.15.4

Compare Source

What's Changed

Last 2.x patch - releasing since the @babel/runtime vulnerability is showing up in some security scans. Hoping to release 3.0 on 6/22 🚀

Fix
  • X/YAxis: fix issue where recharts class names did not get passed to custom tick components by @​MyungAe in #​5840
  • Bar: allow minPointSize function to receive null and undefined values by @​eino in #​5947
  • TypeScript: fix issue which caused build errors when allowSyntheticDefaultImports: false by @​tfaller in #​5810
Security
  • resolve @​babel/runtime ReDoS vulnerability (SNYK-JS-BABELRUNTIME-10044504) by @​moehaje in #​5969
    • recharts isn't vulnerable to this per-se, but it does show up in security tooling like snyk

New Contributors

Full Changelog: recharts/recharts@v2.15.3...v2.15.4

v2.15.3

Compare Source

Last patch release before 3.0 🚀

What's Changed

Fix
  • XAxis: fix padding calculation for padding="gap" and padding="no-gap" when XAxis is type number by @​jackfletch in #​5759

Full Changelog: recharts/recharts@v2.15.2...v2.15.3

v2.15.2

Compare Source

What's Changed

Few bugfixes and bug fix backports for 2.x

Fix
  • Bar/Rectangle: add index back to Bar Rectangle key to prevent duplicate key issues by @​ckifer in #​5561
  • Dot: re-include points object in dotProps by @​brodriguezmilla in #​5657
  • Tooltip: add SVGProps to Tooltip payload type to account for svg properties such as opacity passed by the user by @​ally1002 in #​5712
  • Tooltip/Bar: fix activeBar prop not working when tooltip shared={false} by @​nizans in #​5718
  • General: allow data-* props to be spread on svg elements and not be filtered out by @​prtmwrkr in #​5666

New Contributors

Full Changelog: recharts/recharts@v2.15.1...v2.15.2

v2.15.1

Compare Source

What's Changed

Quick patch release, nothing crazy going on here.

In the meantime please help us test recharts 3.0 alpha #​5445 🚀

Fix
Chore

New Contributors

Full Changelog: recharts/recharts@v2.15.0...v2.15.1


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel

vercel Bot commented Aug 8, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
v0-portfolio Error Error Jun 11, 2026 3:06pm
whale-manager Error Error Jun 11, 2026 3:06pm

@socket-security

socket-security Bot commented Aug 13, 2025

Copy link
Copy Markdown

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 High
Obfuscated code: npm @libsql/client-wasm is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/@libsql/client-wasm@0.17.3

ℹ Read more on: This package | This alert | What is obfuscated code?

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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@libsql/client-wasm@0.17.3. 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.

Warn High
Obfuscated code: npm @prisma/client is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/@prisma/client@7.8.0

ℹ Read more on: This package | This alert | What is obfuscated code?

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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

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

Warn High
License policy violation: npm bcryptjs under BSD-3-Clause-HP

License: BSD-3-Clause-HP - The applicable license policy does not permit this license (5) (package/LICENSE)

From: package.jsonnpm/bcryptjs@3.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

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

Warn High
Obfuscated code: npm better-sqlite3 is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/better-sqlite3@12.10.0

ℹ Read more on: This package | This alert | What is obfuscated code?

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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

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

Warn High
Obfuscated code: npm drizzle-orm is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/drizzle-orm@0.45.2

ℹ Read more on: This package | This alert | What is obfuscated code?

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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

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

Warn High
Obfuscated code: npm recharts is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/recharts@2.15.4

ℹ Read more on: This package | This alert | What is obfuscated code?

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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

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

@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from b415a46 to 7b9b2c4 Compare January 23, 2026 20:40
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from 7b9b2c4 to 17d6e5d Compare February 2, 2026 19:58
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from 17d6e5d to 86d7cb5 Compare February 12, 2026 11:54
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from 86d7cb5 to 2ab4526 Compare February 17, 2026 17:37
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from 2ab4526 to a4ca96a Compare March 5, 2026 15:41
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from a4ca96a to b0ed8ea Compare March 13, 2026 15:03
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from b0ed8ea to bf7579d Compare April 1, 2026 16:41
@renovate renovate Bot changed the title fix(deps): update dependency recharts to v2.15.4 Update dependency recharts to v2.15.4 Apr 8, 2026
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from bf7579d to 3579a07 Compare April 8, 2026 16:44
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from 3579a07 to 1293d47 Compare April 29, 2026 20:49
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from 1293d47 to 45638dd Compare May 12, 2026 09:38
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from 45638dd to 774cfde Compare May 18, 2026 09:27
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from 774cfde to 51c16fe Compare May 28, 2026 21:11
@renovate renovate Bot force-pushed the renovate/recharts-2.x branch from 51c16fe to c9d4c54 Compare June 1, 2026 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants