chore: bump sor to 4.8.0 - feat: migrate base tenderly to new endpoint

[jsy1218]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  feature

• What is the current behavior? (You can also link to an open issue here)
  we don't support new tenderly endpoint on base yet.

• What is the new behavior (if this is a feature change)?
  we will support new tenderly endpoint on base

• Other information:

[jsy1218]

• chore: bump sor to 4.8.0 - feat: migrate base tenderly to new endpoint #762 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jsy1218 and the rest of your teammates on Graphite

[graphite-app]

Graphite Automations

"Request reviewers once CI passes on smart-order-router repo" took an action on this PR • (11/08/24)

3 reviewers were added and 1 assignee was added to this PR based on 's automation.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, filesystem, network, shell Transitive: eval, unsafe	+245	165 MB	kanej

🚮 Removed packages: 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	CI
Filesystem access	npm/[email protected]	Module: fs/promises Location: Package overview	package-lock.json package.json	⚠︎
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	package-lock.json package.json	⚠︎
Filesystem access	npm/[email protected]	Module: fs/promises Location: Package overview	package-lock.json package.json	⚠︎
Dynamic require	npm/[email protected]	Location: Package overview	package-lock.json package.json	⚠︎

View full report↗︎

Next steps

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is dynamic require?

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable 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/[email protected]
• @SocketSecurity ignore npm/[email protected]