Updated dependencies, webhook payloads, hints for agents

[jesushernandez]

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
	mintlify@​4.2.31 ⏵ 4.2.342	-43		+1	+2
	@​types/​node@​22.15.3 ⏵ 22.5.5
	tsx@​4.19.4 ⏵ 4.21.0	+8		+1
	form-data@​4.0.2 ⏵ 4.0.5		+75	+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 @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/mintlify@4.2.342 → npm/@mintlify/cli@4.0.946 ℹ 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.946. 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/mintlify@4.2.342 → npm/@mintlify/common@1.0.661 ℹ 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.661. 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/mintlify@4.2.342 → npm/@mintlify/common@1.0.722 ℹ 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.722. 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/mintlify@4.2.342 → npm/@mintlify/link-rot@3.0.882 ℹ 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.882. 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/mintlify@4.2.342 → npm/@mintlify/models@0.0.255 ℹ 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.255. 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/mintlify@4.2.342 → npm/@mintlify/models@0.0.271 ℹ 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.271. 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/mintlify@4.2.342 → npm/@mintlify/prebuild@1.0.858 ℹ 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.858. 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/mintlify@4.2.342 → npm/@mintlify/previewing@4.0.915 ℹ 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.915. 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/mintlify@4.2.342 → npm/@mintlify/scraping@4.0.522 ℹ 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.522. 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/mintlify@4.2.342 → npm/@mintlify/scraping@4.0.583 ℹ 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.583. 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/mintlify@4.2.342 → npm/@mintlify/validation@0.1.555 ℹ 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.555. 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/mintlify@4.2.342 → npm/@mintlify/validation@0.1.591 ℹ 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.591. 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 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/mintlify@4.2.342 ℹ 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@4.2.342. 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: pnpm-lock.yaml → npm/mintlify@4.2.342 → 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.

View full report