new repo install deps

[alecsavvy]

Description

• uses gookme instead of mookme. see: https://mookme.org/#what-is-mookme
• skips android deps on skip pod install as well

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide repro instructions & any configuration.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1eece57

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​babel-traverse@​6.26.0
	npm/​@​babel/​traverse@​7.27.0 ⏵ 7.18.0		-75
	npm/​axios@​1.7.4 ⏵ 0.18.1	+1	-19
	npm/​available-typed-arrays@​1.0.5
	npm/​array-flatten@​1.1.1
	npm/​array-includes@​3.1.5
	npm/​boolbase@​1.0.0
	npm/​babel-helper-optimise-call-expression@​6.24.1
	npm/​@​truffle/​error@​0.1.0
	npm/​apollo-datasource@​3.3.2
	npm/​babel-helper-get-function-arity@​6.24.1
	npm/​at-least-node@​1.0.0
	npm/​babel-helper-regex@​6.26.0
	npm/​@​redux-saga/​deferred@​1.2.1
	npm/​@​redux-saga/​delay-p@​1.2.1
	npm/​babel-helper-builder-binary-assignment-operator-visitor@​6.24.1
	npm/​@​truffle/​db-loader@​0.2.12
	npm/​@​apollo/​utils.printwithreducedwhitespace@​2.0.1 ⏵ 1.1.0	+1		-7
	npm/​@​resolver-engine/​imports-fs@​0.2.2
	npm/​@​apollo/​utils.dropunuseddefinitions@​2.0.1 ⏵ 1.1.0			-11
	npm/​@​redux-saga/​symbols@​1.1.3
	npm/​babel-helper-call-delegate@​6.24.1
	npm/​babel-helper-hoist-variables@​6.24.1
	npm/​@​types/​mime@​3.0.1
	npm/​babel-helper-explode-assignable-expression@​6.24.1
	npm/​@​apollo/​utils.sortast@​2.0.1 ⏵ 1.1.0			-7
	npm/​@​types/​responselike@​1.0.0
	npm/​@​truffle/​blockchain-utils@​0.1.3
	npm/​@​redux-saga/​is@​1.1.3
	npm/​@​protobufjs/​inquire@​1.1.0
	npm/​@​resolver-engine/​fs@​0.2.1
	npm/​@​apollo/​utils.stripsensitiveliterals@​2.0.1 ⏵ 1.2.0			-9
	npm/​@​resolver-engine/​core@​0.2.1
See 269 more rows in the dashboard

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		npm/@babel/[email protected] has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2; >= 8.0.0-alpha.0 < 8.0.0-alpha.4 Patched version: 7.23.2 From: monitoring/prometheus/package-lock.json → npm/@babel/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? 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 [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/[email protected]. 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.
Block		npm/[email protected] has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: >= 0 Patched version: No patched versions From: package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? 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 [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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.
Block		npm/@protobufjs/[email protected] is a AI-detected potential code anomaly. Notes: The code uses eval to dynamically require a module, which is highly unusual and considered unsafe. The usage of eval can lead to code injection vulnerabilities if the moduleName is not properly validated. Additionally, the use of string manipulation to form 'require' is a form of obfuscation and makes the code harder to read and understand. Confidence: 1.00 Severity: 0.60 From: solana-programs/staking-bridge/yarn.lock → npm/@protobufjs/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@protobufjs/[email protected]. 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.
Block		npm/[email protected] is a AI-detected potential code anomaly. Notes: The code represents a conventional, non-obfuscated part of AJV’s custom keyword support. No direct malicious actions are evident within this module. Security concerns mainly arise from the broader supply chain: the external rule implementation (dotjs/custom), the definition schema, and any user-supplied keyword definitions. The dynamic compilation path (compile(metaSchema, true)) should be exercised with trusted inputs. Recommended follow-up: review the contents of the external modules and monitor the inputs supplied to addKeyword/definitionSchema to ensure no unsafe behavior is introduced during validation or data handling. Confidence: 1.00 Severity: 0.60 From: monitoring/prometheus/package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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		npm/[email protected] has a GitHub dependency. Dependency: websocket@github:web3-js/WebSocket-Node@#polyfi Location: Package overview From: contracts/package-lock.json → npm/@openzeppelin/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What are GitHub dependencies? 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 [email protected]. Suggestion: Publish the GitHub dependency to npm or a private package repository and consume it from there. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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

[raymondjacobson]

maybe we can rename the var, but lgtm!

[alecsavvy]

good idea @raymondjacobson , renamed to SKIP_MOBILE_DEPS

[schottra]

Where did all of these added packages come from? Seems like just removing mookme shouldn't have resulted in installing all of this? I guess some of this might be hoisted packages from recomputing the tree, but it seems like a big diff.

Did you run npm uninstall @escape.tech/mookme or was this a delete from package.json and run a full install situation?

[schottra]

Not seeing where this tool actually gets installed?