fix: resolve Dependabot vulnerabilities

[andy-t-wang]

Summary

• Update mint from 4.2.429 to 4.2.435
• Add pnpm overrides for 10 vulnerable transitive dependencies: cookie, express, flatted, js-yaml, lodash, qs, send, serve-static, tar, zod
• Resolves 11 of 17 open Dependabot alerts (remaining 6 are tar 7.x alerts that can't be fixed until upstream @mintlify/previewing updates)

Test plan

• pnpm install succeeds
• mint version runs without errors
• Verify Dependabot alerts are dismissed after merge

🤖 Generated with Claude Code

[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 @mintlify/cli under Elastic-2.0 License: Elastic-2.0 - the applicable license policy does not allow this license (4) (npm metadata) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/LICENSE) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/mint@4.2.435 → npm/@mintlify/cli@4.0.1038 ℹ 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/@mintlify/cli@4.0.1038. 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 @mintlify/common under Elastic-2.0 License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/LICENSE) From: pnpm-lock.yaml → npm/mint@4.2.435 → npm/@mintlify/common@1.0.804 ℹ 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/@mintlify/common@1.0.804. 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 @mintlify/link-rot under Elastic-2.0 License: Elastic-2.0 - the applicable license policy does not allow this license (4) (npm metadata) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/LICENSE) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/mint@4.2.435 → npm/@mintlify/link-rot@3.0.972 ℹ 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/@mintlify/link-rot@3.0.972. 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 @mintlify/models under Elastic-2.0 License: Elastic-2.0 - the applicable license policy does not allow this license (4) (npm metadata) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/LICENSE) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/mint@4.2.435 → npm/@mintlify/models@0.0.286 ℹ 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/@mintlify/models@0.0.286. 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 @mintlify/prebuild under Elastic-2.0 License: Elastic-2.0 - the applicable license policy does not allow this license (4) (npm metadata) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/LICENSE) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/mint@4.2.435 → npm/@mintlify/prebuild@1.0.943 ℹ 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/@mintlify/prebuild@1.0.943. 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 @mintlify/previewing under Elastic-2.0 License: Elastic-2.0 - the applicable license policy does not allow this license (4) (npm metadata) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/LICENSE) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/mint@4.2.435 → npm/@mintlify/previewing@4.0.1001 ℹ 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/@mintlify/previewing@4.0.1001. 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 @mintlify/scraping under Elastic-2.0 License: Elastic-2.0 - the applicable license policy does not allow this license (4) (npm metadata) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/LICENSE) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/mint@4.2.435 → npm/@mintlify/scraping@4.0.666 ℹ 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/@mintlify/scraping@4.0.666. 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 @mintlify/validation under Elastic-2.0 License: Elastic-2.0 - the applicable license policy does not allow this license (4) (npm metadata) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/mint@4.2.435 → npm/@mintlify/validation@0.1.638 ℹ 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/@mintlify/validation@0.1.638. 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 mint under Elastic-2.0 License: Elastic-2.0 - the applicable license policy does not allow this license (4) (npm metadata) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/LICENSE) License: Elastic-2.0 - the applicable license policy does not allow this license (4) (package/package.json) From: package.json → npm/mint@4.2.435 ℹ 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/mint@4.2.435. 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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c9f514a027

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Do not force front-matter onto js-yaml v4

The new override "js-yaml": ">=4.1.1" upgrades all consumers to v4, and pnpm-lock.yaml now wires front-matter@4.0.2 (used by @mintlify/previewing) to js-yaml: 4.1.1 (pnpm-lock.yaml lines 4749-4755 and 6365-6367). front-matter@4.0.2 depends on js-yaml@^3.13.1 and calls parser.safeLoad in its parser path; in js-yaml v4 that API is removed/throws, so parsing docs with YAML front matter will fail at runtime in preview/build flows.

Useful? React with 👍 / 👎.