Update dependency lottie-react to v2.4.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lottie-react (source)	2.4.0 -> 2.4.1

---

Release Notes

Gamote/lottie-react (lottie-react)

v2.4.1

Compare Source

What's Changed

• feat: update peerDependencies to support React 19 by @​KLXYinc in https://github.com/Gamote/lottie-react/pull/121

New Contributors

• @​KLXYinc made their first contribution in https://github.com/Gamote/lottie-react/pull/121

Full Changelog: Gamote/lottie-react@v2.4.0...v2.4.1

---

Configuration

📅 Schedule: 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 is behind base branch, 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.

[netlify]

✅ Deploy Preview for dev-astral canceled.

Name	Link
🔨 Latest commit	f6488fc
🔍 Latest deploy log	https://app.netlify.com/sites/dev-astral/deploys/67cb3b14b34e7000084cfb14

[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	CI
Obfuscated code	npm/@polkadot/[email protected]	Confidence: 0.91 Location: Package overview	explorer/package.json explorer/yarn.lock	⚠︎

View full report↗︎

Next steps

What is obfuscated code?

Obfuscated files are intentionally packed to hide their behavior. This could be a sign of malware.

Packages should not obfuscate their code. Consider not using packages with obfuscated code.

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/@polkadot/[email protected]

[socket-security]

Report too large to display inline

View full report↗︎