chore: Update Pagefind to 1.3.0

[davidmytton]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
arcjet-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 20, 2024 3:47pm

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, shell	+5	351 MB	bigelowcc

🚮 Removed packages: 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
New author	npm/[email protected]	New Author: lpinca Previous Author: 3rdeden	package-lock.json package.json	🚫
New author	npm/[email protected]	New Author: charlesrea Previous Author: jake.lacey	package-lock.json package.json	🚫
Deprecated	npm/@humanwhocodes/[email protected]	Reason: Use @eslint/object-schema instead	package-lock.json package.json	🚫
Deprecated	npm/@humanwhocodes/[email protected]	Reason: Use @eslint/config-array instead	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: globalThis["fetch"] Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: http Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: https Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: http Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: https Location: Package overview	package-lock.json package.json	🚫
Deprecated	npm/[email protected]	Reason: This version is no longer supported. Please see https://eslint.org/version-support for other options.	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: https Location: Package overview	package-lock.json package.json	🚫
Network access	npm/@browserbasehq/[email protected]	Module: globalThis["fetch"] Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: net Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: http Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: https Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: tls Location: Package overview	package-lock.json package.json	🚫
Shell access	npm/[email protected]	Module: child_process Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: http2 Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: dns Location: Package overview	package-lock.json package.json	🚫
Shell access	npm/@browserbasehq/[email protected]	Module: child_process Location: Package overview	package-lock.json package.json	🚫

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.

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 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.

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]
• @SocketSecurity ignore npm/@humanwhocodes/[email protected]
• @SocketSecurity ignore npm/@humanwhocodes/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@browserbasehq/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@browserbasehq/[email protected]

[blaine-arcjet]

I'm seeing the same error about mime types in the deploy preview

[davidmytton]

This doesn't fix the issue in #332 unfortunately.