chore: update peer dependencies

[marco10024]

In this PR:

• Bug fix (non-breaking change which fixes an issue)

Issues reference:

• fastify peer dependency >=4 #177

Checklist:

• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you lint your code with pnpm lint locally prior to submission?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you successfully ran tests with pnpm test of your changes locally?

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/fastify@5.0.0	Transitive: environment, eval, filesystem, unsafe	+57	7.97 MB	matteo.collina

🚮 Removed packages: npm/fastify@4.21.0

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	CI
Environment variable access	npm/thread-stream@3.1.0	Env Vars: NODE_V8_COVERAGE Location: Package overview	package.json pnpm-lock.yaml	🚫
New author	npm/safe-regex2@4.0.0	New Author: jsumners Previous Author: matteo.collina	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/pino@9.4.0	Env Vars: NODE_V8_COVERAGE Location: Package overview	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/pino@9.4.0	Env Vars: V8_COVERAGE Location: Package overview	package.json pnpm-lock.yaml	🚫
Uses eval	npm/find-my-way@9.1.0	Eval Type: Function Location: Package overview	package.json pnpm-lock.yaml	🚫

View full report↗︎

Next steps

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

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 dynamic code execution?

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code.

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/thread-stream@3.1.0
• @SocketSecurity ignore npm/safe-regex2@4.0.0
• @SocketSecurity ignore npm/pino@9.4.0
• @SocketSecurity ignore npm/find-my-way@9.1.0

[mattkrins]

@alemagio who can merge this?