Mercurial
view third_party/libuv/SECURITY.md @ 279:b3b547563ec7
Add Google connector service and agent wiki
Implement the C/Seobeo Google Drive and Gmail connector with encrypted OAuth storage, Zenbu authentication, browser testing, AI tool discovery, chunked HTTP decoding, and Bazel coverage. Consolidate repository guidance into progressive wiki documentation and enforce arena-first allocation for new first-party C code.
Co-authored-by: Copilot <[email protected]>
Copilot-Session: 84c338fd-0939-4bb3-b7f3-1062eb213e5d
| author | MrJuneJune <me@mrjunejune.com> |
|---|---|
| date | Mon, 17 Aug 2026 22:22:36 -0700 |
| parents | 948de3f54cea |
| children |
line wrap: on
line source
# Security Policy ## Supported Versions Currently, we are providing security updates for the latest release in the v1.x series: | Version | Supported | | ------- | ------------------ | | Latest v1.x | :white_check_mark: | ## Reporting a Vulnerability If you believe you have found a security vulnerability in `libuv`, please use the [GitHub's private vulnerability reporting feature](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability#privately-reporting-a-security-vulnerability) in the [libuv repository](https://github.com/libuv/libuv) to report it to us. This will allow us to assess the risk, and make a fix available before we add a bug report to the GitHub repository. Please do: * Provide as much information as you can about the vulnerability. * Provide details about your configuration and environment, if applicable. Please do not: * Post any information about the vulnerability in public places. * Attempt to exploit the vulnerability yourself. We take all security bugs seriously. Thank you for improving the security of `libuv`. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.