CDP-6026: force transitive uuid to ^11.1.1 to resolve Dependabot alert

[jcpsimmons]

Summary

Resolves Dependabot alert #40 (medium severity: missing buffer bounds check in uuid v3/v5/v6 when buf is provided).

uuid@8.3.2 enters the dependency tree only as a devDep transitive: nyc -> istanbul-lib-processinfo -> uuid. Its vulnerable code path (the buf parameter to v3/v5/v6) is not reached by nyc's usage, so the real exposure is essentially zero. The shipped SDK has no dependency on uuid at all. Still, an overrides entry in package.json is the cheapest way to silence the security tab without a wider toolchain bump.

Test plan

• npm install reports 0 vulnerabilities
• npm ls uuid shows the override taking effect (uuid@11.1.1 overridden)
• npm run build clean
• npm test passes, nyc 100% coverage gate holds

The change is two files: package.json (new overrides block) and package-lock.json (regenerated lockfile).

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	husky@​8.0.1 ⏵ 8.0.3	+1		+1
	@​types/​node@​22.19.18 ⏵ 22.19.19	+1		+1
	ts-node@​10.9.1 ⏵ 10.9.2	+1
	typescript@​4.9.4 ⏵ 4.9.5
	prettier@​2.6.2 ⏵ 2.8.8	+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 typescript Location: Package overview From: package-lock.json → npm/typescript@4.9.5 ℹ 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@4.9.5. 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