fix: Downgrade Astro v5 to v4

[davidmytton]

Fixes #332

[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 4:19pm

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@astrojs/react@3.6.3	Transitive: environment, eval, filesystem, network, shell, unsafe	+107	495 MB	fredkschott
npm/@astrojs/starlight@0.29.2	Transitive: environment, eval, filesystem, network, shell	+241	29 MB	fredkschott
npm/@astrojs/vercel@7.8.2	Transitive: environment, eval, filesystem, network, shell, unsafe	+137	244 MB	matthewp
npm/astro@4.16.16	Transitive: environment, eval, filesystem, network, shell, unsafe	+356	536 MB	fredkschott

🚮 Removed packages: npm/@astrojs/react@4.1.1, npm/@astrojs/starlight@0.30.3, npm/@astrojs/vercel@8.0.1, npm/astro@5.1.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
New author	npm/kind-of@6.0.3	New Author: doowb Previous Author: jonschlinkert	package-lock.json package.json	🚫
Network access	npm/vite@5.4.11	Module: net Location: Package overview	package-lock.json package.json	🚫
Network access	npm/vite@5.4.11	Module: http Location: Package overview	package-lock.json package.json	🚫
Shell access	npm/vite@5.4.11	Module: child_process Location: Package overview	package-lock.json package.json	🚫
Network access	npm/vite@5.4.11	Module: https Location: Package overview	package-lock.json package.json	🚫
Network access	npm/vite@5.4.11	Module: tls Location: Package overview	package-lock.json package.json	🚫
High CVE	npm/astro@4.16.16	CVE: GHSA-49w6-73cw-chjr Astro's server source code is exposed to the public if sourcemaps are enabled (HIGH) Affected versions: <= 4.16.17 Patched version: 4.16.18	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 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.

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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/kind-of@6.0.3
• @SocketSecurity ignore npm/vite@5.4.11
• @SocketSecurity ignore npm/astro@4.16.16