feat: @lavamoat/git-safe-dependencies

[leotm]

Description

Quality Quest 2024 ft. @naugtur and @tommasini b2b

TODO

• add package
• integrate in CI
• update depcheck
• socket

Related issues

• Fixes: https://github.com/MetaMask/mobile-planning/issues/2079

Manual testing steps

1. Locally update package.json to "react-native-tcp": "aprock/react-native-tcp#11/head"
2. Run yarn git-safe-dependencies
3. There should be an error message
4. Revert package.json to the correct "react-native-tcp": "aprock/react-native-tcp#98fbc801f0586297f16730b2f4c75eef15dfabcd",
5. Run yarn git-safe-dependencies
6. great
7. success

Screenshots/Recordings

Before

e.g. package.json > "react-native-tcp": "aprock/react-native-tcp#11/head",

After

fixed to: package.json > "react-native-tcp": "aprock/react-native-tcp#98fbc801f0586297f16730b2f4c75eef15dfabcd",
in #12595

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@lavamoat/[email protected]	network	0	15.9 kB	lmbot
npm/@yarnpkg/[email protected]	None	0	197 kB	yarnbot
npm/[email protected]	filesystem	0	42.7 kB	lirantal_bot
npm/[email protected]	None	0	58.9 kB	addaleax

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/@lavamoat/[email protected]

View full report↗︎

Next steps

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

[leotm]

@SocketSecurity ignore npm/@lavamoat/[email protected]

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[naugtur]

Looks right

[tommasini]

LOVE IT <3