Hao Zheandzhiheng.liu
f0445e0cce
* docs: fix broken links and anchors across READMEs and guides Sweep findings: D-10, D-11, D-12, D-13, D-14, D-15. Restore valid documentation targets and stable cross-page anchors. (cherry picked from commite3504d633d) * docs: correct contributor and release references Reconstruct the factual parts of draft #3397 against current upstream: use the supported setup wizard, align the repository tree and workflow names with tracked files, document current release paths, and repair the bug-bounty link. Excludes install-policy and subjective content rewrites. Based-on:b332e19e40Based-on:c89afb17f2Co-authored-by: zhiheng.liu <zhiheng.liu@bytedance.com> * build: propagate recipe failures and align CMake minimum Keep build failures visible, use isolated temporary extraction paths, and enforce the native build's CMake 3.15 floor across all contributor guides. CMake version parsing accepts prerelease and vendor suffixes. Based-on:8943a12285Co-authored-by: zhiheng.liu <zhiheng.liu@bytedance.com> * fix(scripts): surface backfill enumeration failures Preserve the safety fix from draft #3415 while retaining legacy no-op arguments for existing operational scripts. Deprecated arguments now remain parse-compatible, advertise their status in help, and emit explicit warnings when used. Based-on:5516d96048Co-authored-by: zhiheng.liu <zhiheng.liu@bytedance.com> --------- Co-authored-by: zhiheng.liu <zhiheng.liu@bytedance.com>
1.7 KiB
Security and privacy
If you discover potential security issues in the project, or believe you may have found a security issue, please notify the ByteDance security team through our security center or vulnerability reporting email. Please do not create public GitHub Issues.
We will assess the vulnerability based on the Common Vulnerability Scoring System (CVSS 3.1). The security team will keep you updated on key progress and may request further information or guidance from you. You are welcome to contact us via the email or website mentioned above to ask questions or discuss disclosure matters.
To protect the security of our customers, ByteDance requests that you do not publish or share information regarding the vulnerability in any public forum, nor publish or share data involving users, until the vulnerability has been remediated and our users have been notified. Please understand that the time required for remediation depends on the severity of the vulnerability and the scope of the impact.
Individuals, companies, and security teams may wish to publish security advisories on their own websites or other forums. Please contact us via the email or website mentioned above prior to publication to discuss the information that can be disclosed and to coordinate the disclosure timeline.
Bug Bounty Reward
The bug bounty reward policy ("ByteDance Security Response Center Security Report Handling Rules") is published on the security center. If you have any questions about the rules, please contact us there or via src@bytedance.com.