Fix sync, update dependencies, fix org creation

[TheLastCicada]

No description provided.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​babel/​plugin-syntax-import-attributes@​7.27.1 ⏵ 7.28.6
	@​commitlint/​cli@​20.3.0 ⏵ 20.4.1				+4
	lodash@​4.17.21 ⏵ 4.17.23	-5	+2	+1
	@​babel/​register@​7.28.3 ⏵ 7.28.6
	@​babel/​preset-env@​7.28.5 ⏵ 7.29.0
	@​babel/​cli@​7.28.3 ⏵ 7.28.6
	@​babel/​eslint-parser@​7.28.5 ⏵ 7.28.6				+1
	@​babel/​core@​7.28.5 ⏵ 7.29.0
	express-rate-limit@​8.2.1
	globals@​17.0.0 ⏵ 17.3.0	+1		+1	+5
	cors@​2.8.5 ⏵ 2.8.6
	body-parser@​2.2.1 ⏵ 2.2.2	+1		+1	-1
	superagent@​10.2.3 ⏵ 10.3.0	+1			-1
	prettier@​3.7.4 ⏵ 3.8.1			+1
	@​yao-pkg/​pkg@​6.11.0 ⏵ 6.12.0				+1
	supertest@​7.1.4 ⏵ 7.2.2			+1	-2
	@​commitlint/​config-conventional@​20.3.0 ⏵ 20.4.1				+4
	mysql2@​3.16.0 ⏵ 3.16.3

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 meow under CC-BY-3.0 License: CC-BY-3.0 - the applicable license policy does not allow this license (4) (package/build/licenses.md) From: package-lock.json → npm/@commitlint/config-conventional@20.4.1 → npm/@commitlint/cli@20.4.1 → npm/meow@13.2.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/meow@13.2.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		Potential code anomaly (AI signal): npm @babel/core is 100.0% likely to have a medium risk anomaly Notes: The examined code is a standard, benign helper for constructing and wrapping configuration items from descriptors within Babel’s tooling. There is no evidence of data leakage, exfiltration, backdoors, or other malicious activity in this fragment. The combination of immutability, brand-based identity, and non-enumerable descriptor storage indicates a well-scoped internal utility rather than anything suspicious. Confidence: 1.00 Severity: 0.60 From: package-lock.json → npm/@babel/core@7.29.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/core@7.29.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		Potential code anomaly (AI signal): npm @yao-pkg/pkg is 80.0% likely to have a medium risk anomaly Notes: The code involves dynamically executing JavaScript code using the vm.Script module and managing child processes to handle this execution. This approach is inherently risky as it allows for arbitrary code execution and has potential security implications if the input data is not properly sanitized. However, there are no explicit signs of malicious intent such as data theft or system damage. The main concerns are related to the potential misuse of dynamic code execution and process management, which could be exploited in a supply chain attack scenario. Confidence: 0.80 Severity: 0.65 From: package-lock.json → npm/@yao-pkg/pkg@6.12.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yao-pkg/pkg@6.12.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		Potential code anomaly (AI signal): npm @yao-pkg/pkg is 72.0% likely to have a medium risk anomaly Notes: The fragment implements a sophisticated packaging/assembly mechanism for bundling a virtual filesystem with optional native binaries. While legitimate in advanced packaging tools, the combination of dynamic prelude injection, on-disk binary manipulation (bak/overwrite), and environment-driven external binary installation creates meaningful supply-chain security risk. The absence of explicit exfiltration or hard-coded secrets does not mitigate the risk of hidden Payload/Code injection in a build pipeline. Recommend thorough provenance checks, strict controls around prebuild-install, explicit documentation of dynamic payload embedding, and integrity verification (signatures, hashes) of all artifacts involved. Confidence: 0.72 Severity: 0.60 From: package-lock.json → npm/@yao-pkg/pkg@6.12.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yao-pkg/pkg@6.12.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.

View full report