Output types for ESM and CJS separately

[Mrtenz]

No description provided.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@andrewbranch/untar.js@1.0.3	None	0	10.7 kB	andrewbranch
npm/@arethetypeswrong/cli@0.15.1	Transitive: environment, filesystem, shell	+35	37.3 MB	andrewbranch
npm/@arethetypeswrong/core@0.15.1	None	+8	33.2 MB	andrewbranch
npm/@colors/colors@1.5.0	environment	0	39.5 kB	dabh
npm/@sindresorhus/is@4.6.0	None	0	57.5 kB	sindresorhus
npm/ansicolors@0.3.2	None	0	7.46 kB	thlorenz
npm/cardinal@2.1.1	filesystem	+3	450 kB	thlorenz
npm/cli-table3@0.6.3	Transitive: environment	+6	159 kB	speedytwenty
npm/commander@10.0.1	environment, filesystem, shell	0	174 kB	abetomo
npm/emojilib@2.4.0	None	0	327 kB	muan
npm/fflate@0.8.2	None	0	773 kB	101arrowz
npm/marked-terminal@6.3.0	Transitive: environment	+20	3.82 MB	mikaelb
npm/marked@9.1.6	None	0	914 kB	tonybrix
npm/node-emoji@2.1.3	None	+5	457 kB	omnidan
npm/prompts@2.4.2	None	+1	197 kB	terkelg
npm/redeyed@2.1.1	None	+1	376 kB	thlorenz
npm/skin-tone@2.0.0	None	+1	7.99 kB	sindresorhus
npm/supports-hyperlinks@3.0.0	environment	+2	18.9 kB	sindresorhus
npm/ts-expose-internals-conditionally@1.0.0-empty.0	None	0	909 B	andrewbranch
npm/unicode-emoji-modifier-base@1.0.0	None	0	3.25 kB	mathias
npm/validate-npm-package-name@5.0.0	None	+3	122 kB	lukekarrys

🚮 Removed packages: npm/sisteransi@1.0.5

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
New author	npm/validate-npm-package-name@5.0.0	New Author: lukekarrys Previous Author: gar
Deprecated	npm/marked-terminal@6.3.0	Reason: should have been major release. Use 7.0.0

View full report↗︎

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

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/validate-npm-package-name@5.0.0
• @SocketSecurity ignore npm/marked-terminal@6.3.0

[Mrtenz]

#182.