fix(ci): repair CI (lockfile, CVE overrides, SPDX headers)

[igorjs]

Repairs main CI end to end after the repo-config hardening apply: lockfile regen (autoInstallPeers/tarball mismatch), CVE overrides (ws>=8.21.0, undici>=7.28.0, brace-expansion>=5.0.6), SPDX headers on bin/tests/scripts, and a .license-checker.allow for the dep-license gate. Verified: lint-and-test, deny + spdx, and scan all pass.

Closes #22

[github-actions]

PR Quality Gate: no linked issue

Every PR must reference an issue that describes the motivation for the change.

Add a closing reference to your PR description:

Closes #N

Replace N with the issue number. If no issue exists yet, please open one first.

[github-actions]

PR Quality Gate: no linked issue

Every PR must reference an issue that describes the motivation for the change.

Add a closing reference to your PR description:

Closes #N

Replace N with the issue number. If no issue exists yet, please open one first.

[github-actions]

PR Quality Gate: no linked issue

Every PR must reference an issue that describes the motivation for the change.

Add a closing reference to your PR description:

Closes #N

Replace N with the issue number. If no issue exists yet, please open one first.

[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		Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/miniflare@4.20260603.0 → npm/@emnapi/runtime@1.11.1 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.11.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		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/c8@11.0.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.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.

View full report