add funding.json for op retro program

[Yash094]

---

PR-Codex overview

This PR introduces a new funding.json configuration and updates the package-lock.json file to include various dependencies and their versions, enhancing project management and dependency tracking.

Detailed summary

• Added funding.json with opRetro configuration and a projectId.
• Updated package-lock.json to include new dependencies such as biome, @biomejs/biome, and various @changesets packages.
• Specified versions and licenses for new dependencies.

The following files were skipped due to too many changes: package-lock.json

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

⚠️ No Changeset found

Latest commit: d5d330b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• merge-queue - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[vercel]

@Yash094 is attempting to deploy a commit to the thirdweb Team on Vercel.

A member of the Team first needs to authorize it.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 41.73%. Comparing base (f693ab8) to head (d5d330b).
Report is 27 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #6353       +/-   ##
===========================================
- Coverage   56.83%   41.73%   -15.11%     
===========================================
  Files        1168     1167        -1     
  Lines       64793    65191      +398     
  Branches     5258     3842     -1416     
===========================================
- Hits        36824    27205     -9619     
- Misses      27242    37285    +10043     
+ Partials      727      701       -26     

Flag	Coverage Δ		*Carryforward flag
legacy_packages	65.68% <ø> (ø)		Carriedforward from 85a4108
packages	36.93% <ø> (-18.12%)	⬇️

*This pull request uses carry forward flags. Click here to find out more.

see 267 files with indirect coverage changes

[jakeloo]

Run formatter on the funding.json file

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, filesystem, shell Transitive: eval, network, unsafe	+68	6.44 MB	1egoman

View full report↗︎

Have feedback? Participate in our User Experience Survey 📊

[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
Critical CVE	npm/[email protected]	CVE: GHSA-jf85-cpcp-j695 Prototype Pollution in lodash (CRITICAL) Affected versions: < 4.17.12 Patched version: 4.17.12	package-lock.json	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

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

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]