{{ message }}
Repository navigation
Trying to get in touch regarding a security issue #26
Description
Hey there!
I belong to an open source security research community, and a member (@0xAmal) has found an issue, but doesn’t know the best way to disclose it.
If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.
Thank you for your consideration, and I look forward to hearing from you!
(cc @huntr-helper)
Activity
tianzhou commentedon Oct 11, 2021
Hi zidingz, thanks for contacting us. We just added https://github.com/bytebase/bytebase/blob/main/SECURITY.md. And please contact us at support@bytebase.com
test(advisor/tidb): pin cumulative #26 — UNION outer-LIMIT UX improve…
refactor(advisor/tidb): migrate statement family pair to omni AST (Ph…
refactor(advisor/tidb): migrate cross-stmt column-state pair to omni …
test(advisor/tidb): pin cumulative #29 — parenthesized-column wrappin…
refactor(advisor/tidb): migrate index_no_duplicate_column to omni AST…
fix(advisor/tidb): SET-clause target extraction + canonicalized group…
refactor(advisor/tidb): migrate builtin_prior_backup_check to omni AS…