feat: add new custom configuration for routes

[matteovivona]

No description provided.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@biomejs/[email protected]	shell	0	118 kB	dominionl
npm/@types/[email protected] 🔁 npm/@types/[email protected]	None	+1	2.39 MB	types
npm/[email protected] 🔁 npm/[email protected]	None	0	22.7 MB	typescript-bot

🚮 Removed packages: npm/@typescript-eslint/[email protected], npm/@typescript-eslint/[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	CI
Shell access	npm/@biomejs/[email protected]	Module: child_process Location: Package overview	package.json pnpm-lock.yaml	🚫
Dynamic require	npm/@biomejs/[email protected]	Location: Package overview	package.json pnpm-lock.yaml	🚫
Uses eval	npm/[email protected]	Eval Type: Function Location: Package overview	package.json pnpm-lock.yaml	🚫
New author	npm/[email protected]	New Author: ljharb Previous Author: eduardorfs	package.json pnpm-lock.yaml	🚫
Unstable ownership	npm/[email protected]	Author: ljharb	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/@babel/[email protected]	Env Vars: FORCE_COLOR Location: Package overview	package.json pnpm-lock.yaml	🚫
AI-detected potential code anomaly	npm/[email protected]	Notes: The code sets up signal listeners to handle termination signals in a Node.js process and execute a provided callback. While it does not contain overtly malicious behavior, there are some suspicious elements and potential risks. The use of empty try/catch blocks to ignore errors could hide issues. Killing the process with the received signal and setting an empty timeout afterwards is unusual and raises questions about the code's intent. Increasing the max listeners count could also be used to circumvent listener limits. However, without more context about the intended use case, it's difficult to conclude definitively that this code is malicious. The suspicious behaviors warrant caution and further review to determine if they could be exploited for malicious purposes. Confidence: 1.00 Severity: 0.60	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: GIT_SSH_COMMAND Location: Package overview	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: GIT_ASKPASS Location: Package overview	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: BROWSER Location: Package overview	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: FAKE_FS_O_FILENAME Location: Package overview	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: TESTING_RIMRAF_NODE_VERSION Location: Package overview	package.json pnpm-lock.yaml	🚫
Network access	npm/[email protected]	Module: net Location: Package overview	package.json pnpm-lock.yaml	🚫
Unstable ownership	npm/@fastify/[email protected]	Author: fdawgs	package.json pnpm-lock.yaml	🚫
New author	npm/@fastify/[email protected]	New Author: fdawgs Previous Author: matteo.collina	package.json pnpm-lock.yaml	🚫
New author	npm/[email protected]	New Author: fdawgs Previous Author: jsumners	package.json pnpm-lock.yaml	🚫
Unstable ownership	npm/[email protected]	Author: fdawgs	package.json pnpm-lock.yaml	🚫
Unstable ownership	npm/[email protected]	Author: fdawgs	package.json pnpm-lock.yaml	🚫
New author	npm/[email protected]	New Author: fdawgs Previous Author: matteo.collina	package.json pnpm-lock.yaml	🚫
New author	npm/[email protected]	New Author: dangreen Previous Author: oss-bot	package.json pnpm-lock.yaml	🚫
Unstable ownership	npm/[email protected]	Author: dangreen	package.json pnpm-lock.yaml	🚫
Unstable ownership	npm/[email protected]	Author: dangreen	package.json pnpm-lock.yaml	🚫
New author	npm/[email protected]	New Author: dangreen Previous Author: oss-bot	package.json pnpm-lock.yaml	🚫

View full report↗︎

Next steps

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is dynamic require?

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.

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.

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 unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

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 an AI-detected potential code anomaly?

AI has identified unusual behaviors that may pose a security risk.

An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

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.

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

[matteovivona]

PR unpublished