ci: enable semantic-release

[ericcrosson-bitgo]

Configure semantic-release to push release candidates on every
push to master.

The release will push an npm package to the @bitgo-forks scope on
npm.

Ticket: BG-66106

[socket-security]

Socket Security Pull Request Report

Dependency issues detected. If you merge this pull request, you will not be alerted to the instances of these issues again.

😵‍💫 Bin script confusion

This package has multiple bin scripts with the same name. This can cause non-deterministic behavior when installing or could be a sign of a supply chain attack

Consider removing one of the conflicting packages. Packages should only export bin scripts with their name

Package	Bin script	Source
[email protected] (added)	rimraf	package.json via [email protected], @semantic-release/[email protected]
[email protected] (added)	rimraf	package.json
[email protected] (added)	rimraf	package.json via [email protected]
[email protected] (added)	semver	package.json via [email protected], @semantic-release/[email protected]
[email protected] (added)	semver	package.json via [email protected]
[email protected] (added)	semver	package.json via [email protected], [email protected]
[email protected] (added)	semver	package.json via [email protected]
[email protected] (added)	node-which	package.json via [email protected], @semantic-release/[email protected]
[email protected] (added)	node-which	package.json via [email protected], [email protected]
[email protected] (added)	mkdirp	package.json via [email protected]
[email protected] (added)	mkdirp	package.json via [email protected], @semantic-release/[email protected]

Pull request report summary

Issue	Status
Install scripts	✅ 0 issues
Native code	✅ 0 issues
Bin script confusion	⚠️ 11 issues
Bin script shell injection	✅ 0 issues
Unresolved require	✅ 0 issues
Invalid package.json	✅ 0 issues
HTTP dependency	✅ 0 issues
Git dependency	✅ 0 issues
Potential typo squat	✅ 0 issues
Known Malware	✅ 0 issues
Telemetry	✅ 0 issues
Protestware/Troll package	✅ 0 issues

Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] [email protected]

• @SocketSecurity ignore [email protected]
• @SocketSecurity ignore [email protected]
• @SocketSecurity ignore [email protected]
• @SocketSecurity ignore [email protected]
• @SocketSecurity ignore [email protected]

Powered by socket.dev