FEAT: Set up auth

[ermish]

Resolves #[Issue number]

all the things

What changed

Testing instructions

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@apollo/[email protected]	environment, network Transitive: eval, filesystem	+70	8.05 MB	apollo-bot
npm/@fastify/[email protected]	None	+2	140 kB	climba03003
npm/@firebase/[email protected]	environment, network Transitive: filesystem	+8	813 kB	google-wombot
npm/@graphql-codegen/[email protected]	environment, filesystem, network, shell, unsafe Transitive: eval	+211	24.5 MB	dotansimha
npm/@graphql-codegen/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+126	19.3 MB	dotansimha
npm/@graphql-codegen/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+127	19.4 MB	dotansimha
npm/@graphql-tools/[email protected]	environment	+5	652 kB	ardatan
npm/@graphql-tools/[email protected]	None	+5	688 kB	ardatan
npm/@swc/[email protected]	environment, filesystem, shell	+12	431 MB	kdy1
npm/@types/[email protected]	None	+10	113 kB	types
npm/@types/[email protected]	None	0	2.09 MB	types
npm/@types/[email protected]	None	+3	41.4 kB	types
npm/[email protected]	Transitive: environment, eval	+21	4.89 MB	matteo.collina
npm/[email protected]	environment, filesystem, network Transitive: shell	+47	27.3 MB	google-wombot
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell	+132	17 MB
npm/[email protected]	Transitive: environment, filesystem, network	+48	105 MB	google-wombot
npm/[email protected]	None	0	170 kB	sindresorhus

🚮 Removed packages: npm/@apollo/[email protected], npm/@firebase/[email protected], npm/@graphql-codegen/[email protected], npm/@graphql-codegen/[email protected], npm/@graphql-codegen/[email protected], npm/@graphql-tools/[email protected], npm/@graphql-tools/[email protected], npm/@swc/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], 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
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	orphan: npm/[email protected]
Install scripts	npm/@swc/[email protected]	Install script: postinstall Source: node postinstall.js	package-lock.json package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: node scripts/postinstall	Source
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	Source
Install scripts	npm/@swc/[email protected]	Install script: postinstall Source: node postinstall.js	Source

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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/@swc/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@swc/[email protected]

[theyokohamalife]

@ermish Is this still in progress?