chore: version packages

[github-actions[bot]]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

mipd@0.1.0

Minor Changes

• #1 dc53151 Thanks @tmm! - Renamed Config type to Register

[socket-security[bot]]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
@size-limit/preset-small-lib	8.2.6	None	+3	143 kB	ai
@changesets/changelog-github	0.4.8	network, filesystem, environment	+8	669 kB	changesets-release-bot
rimraf	5.0.1	filesystem, environment	+2	300 kB	isaacs
@types/fs-extra	11.0.1	None	+1	43.8 kB	types
@vitest/coverage-v8	0.32.2	None	+102	11.9 MB	oreanno
jsdom	22.1.0	eval, network, filesystem, shell	+41	7.02 MB	domenic
fs-extra	11.1.1	None	+2	83.9 kB	ryanzim

🚮 Removed packages: mipd@0.0.4

[socket-security[bot]]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Install scripts	rome	12.1.3	Install script: postinstall Source: node scripts/postinstall.js	package.json
Install scripts	bun	0.5.9	Install script: postinstall Source: node install.js	package.json
Install scripts	simple-git-hooks	2.8.1	Install script: postinstall Source: node ./postinstall.js	package.json

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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore rome@12.1.3
• @SocketSecurity ignore bun@0.5.9
• @SocketSecurity ignore simple-git-hooks@2.8.1