refactor v3 subgraph to include token subgraphs

[mzywang]

No description provided.

[mzywang]

• refactor v3 subgraph to include token subgraphs #259 👈 (View in Graphite)
• main

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

[socket-security]

Report too large to display inline

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
Dynamic require	npm/yargs@17.7.2	Location: Package overview	package.json yarn.lock	⚠︎
Filesystem access	npm/yargs@17.7.2	Module: fs Location: Package overview	package.json yarn.lock	⚠︎
Dynamic require	npm/yargs@17.7.2	Location: Package overview	package.json yarn.lock	⚠︎
Dynamic require	npm/yargs@17.7.2	Location: Package overview	package.json yarn.lock	⚠︎
Filesystem access	npm/yargs@17.7.2	Module: fs Location: Package overview	package.json yarn.lock	⚠︎
Filesystem access	npm/require-directory@2.1.1	Module: fs Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/y18n@5.0.8	Module: fs Location: Package overview	yarn.lock	⚠︎
Socket optimized override available	npm/string.prototype.repeat@1.0.0	cleanup available: Run npx socket optimize	yarn.lock	⚠︎
Dynamic require	npm/@tybys/wasm-util@0.9.0	Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/escalade@3.2.0	Module: fs Location: Package overview	yarn.lock	⚠︎
Dynamic require	npm/@emnapi/runtime@1.3.1	Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/dotenv@16.4.7	Module: fs Location: Package overview	package.json yarn.lock	⚠︎
Filesystem access	npm/fdir@6.4.3	Module: fs Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/glob@7.2.3	Module: fs Location: Package overview	yarn.lock	⚠︎
Dynamic require	npm/eslint-plugin-import@2.31.0	Location: Package overview	yarn.lock	⚠︎

View full report↗︎

Next steps

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.

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.

Using Socket CLI to optimize dependencies

Package can be replaced with a Socket optimized override.

Run `npx socket optimize` in your repository to optimize your 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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/yargs@17.7.2
• @SocketSecurity ignore npm/require-directory@2.1.1
• @SocketSecurity ignore npm/y18n@5.0.8
• @SocketSecurity ignore npm/string.prototype.repeat@1.0.0
• @SocketSecurity ignore npm/@tybys/wasm-util@0.9.0
• @SocketSecurity ignore npm/escalade@3.2.0
• @SocketSecurity ignore npm/@emnapi/runtime@1.3.1
• @SocketSecurity ignore npm/dotenv@16.4.7
• @SocketSecurity ignore npm/fdir@6.4.3
• @SocketSecurity ignore npm/glob@7.2.3
• @SocketSecurity ignore npm/eslint-plugin-import@2.31.0