📘 Update guestbook updates branch

[JFWooten4]

Trying to clear out some of the old PRs because they contain commits I need to continue 723.

Also I think this is kinda funny.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​docusaurus/​tsconfig@​3.8.1 ⏵ 3.9.2				-2
	@​docusaurus/​faster@​3.8.1 ⏵ 3.9.2	+1
	@​docusaurus/​module-type-aliases@​3.8.1 ⏵ 3.9.2				+1
	@​docusaurus/​preset-classic@​3.8.1 ⏵ 3.9.2				+1
	@​docusaurus/​types@​3.8.1 ⏵ 3.9.2			+1
	@​docusaurus/​eslint-plugin@​3.8.1 ⏵ 3.9.2	+1			+2
	@​docusaurus/​core@​3.8.1 ⏵ 3.9.2	+1		+1
	docusaurus-theme-openapi-docs@​4.3.7 ⏵ 4.5.1
	@​docusaurus/​theme-mermaid@​3.8.1 ⏵ 3.9.2			+1
	js-yaml@​4.1.1
	patch-package@​8.0.0 ⏵ 8.0.1	+1		+1
	@​eslint/​eslintrc@​3.3.1 ⏵ 3.3.3
	react@​19.0.0 ⏵ 19.2.3
	@​crowdin/​cli@​4.11.0 ⏵ 4.12.0	+1			+3
	typescript@​5.9.2 ⏵ 5.9.3			+1
	prettier@​3.6.2 ⏵ 3.7.4	-3		+1
	glob@​13.0.1
	react-dom@​19.0.0 ⏵ 19.2.3	+1		+1
	eslint@​9.36.0 ⏵ 9.39.2	+5
	@​docusaurus/​remark-plugin-npm2yarn@​3.8.1 ⏵ 3.9.2	-1			+1
	sass@​1.93.1 ⏵ 1.97.1				-2
	@​eslint/​js@​9.36.0 ⏵ 9.39.2			+10
	docusaurus-plugin-openapi-docs@​4.3.7 ⏵ 4.5.1	+1
	@​redocly/​cli@​1.34.5 ⏵ 2.14.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm diff under BSD-3-Clause Location: Package overview From: ? → npm/@stellar/open-rpc-docs-react@0.2.1 → npm/docusaurus-theme-openapi-docs@4.5.1 → npm/diff@5.2.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: 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@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/diff@5.2.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm json-schema Location: Package overview From: ? → npm/@docusaurus/preset-classic@3.9.2 → npm/json-schema@0.4.0 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: 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@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/json-schema@0.4.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm marked under BSD-3-Clause AND MIT Location: Package overview From: ? → npm/@docusaurus/theme-mermaid@3.9.2 → npm/@docusaurus/preset-classic@3.9.2 → npm/marked@16.4.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: 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@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/marked@16.4.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm node-forge under GPL-2.0 License: GPL-2.0 - the applicable license policy does not allow this license (4) (package/LICENSE) From: ? → npm/@docusaurus/core@3.9.2 → npm/node-forge@1.3.3 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: 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@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-forge@1.3.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm qs under BSD-3-Clause Location: Package overview From: ? → npm/@stellar/open-rpc-docs-react@0.2.1 → npm/docusaurus-theme-openapi-docs@4.5.1 → npm/@docusaurus/core@3.9.2 → npm/qs@6.14.1 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: 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@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/qs@6.14.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm sass Location: Package overview From: package.json → npm/sass@1.97.1 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: 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@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/sass@1.97.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm shelljs under BSD-3-Clause Location: Package overview From: ? → npm/@crowdin/cli@4.12.0 → npm/shelljs@0.10.0 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: 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@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/shelljs@0.10.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm typescript under CC-BY-4.0 License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) From: package.json → npm/typescript@5.9.3 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: 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@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@5.9.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Deprecated by its maintainer: npm tar Reason: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exhorbitant rates) by contacting i@izs.me From: ? → npm/@crowdin/cli@4.12.0 → npm/tar@7.5.6 ℹ Read more on: This package | This alert | What is a deprecated package? Next steps: 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@socket.dev. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tar@7.5.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report