Update CI and related files to match module template

[Mrtenz]

No description provided.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	21.9 kB	bmealey
npm/[email protected]	None	0	976 kB	olivernn
npm/[email protected]	None	0	428 kB	tonybrix
npm/[email protected]	filesystem, network	+4	16.8 MB	antfu
npm/[email protected]	Transitive: filesystem, network	+9	88.4 MB	typedoc-bot
npm/[email protected]	network	0	490 kB	vscode-bot
npm/[email protected]	None	0	347 kB	vscode-bot

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
Network access	npm/[email protected]	Module: globalThis["fetch"] Location: Package overview
New author	npm/[email protected]	New Author: vscode-bot Previous Author: alexandrudima
Network access	npm/[email protected]	Module: globalThis["fetch"] Location: Package overview

View full report↗︎

Next steps

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

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.

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/[email protected]

[mcmire]

One suggestion, but otherwise looks good.

[Mrtenz]

auto-changelog is missing, causing CI to fail. Will address that in a future PR.

[mcmire]

Looks good!