16 Commits (966066b897235579dfbac2d7ce639ea236aa63cc)

Author	SHA1	Message	Date
Louis Lam	8092640e20	Update security report guide (#2762)	2 years ago
Louis Lam	cb953361b1	Update SECURITY.md	2 years ago
Louis Lam	8c684e9293	Update SECURITY.md	2 years ago
Jakob	69d6633e6d	Remove template comment	2 years ago
Louis Lam	5f9f29f527	Update SECURITY.md	3 years ago
Louis Lam	da0eaddeb8	Update SECURITY.md	3 years ago
Louis Lam	234fba3978	Update SECURITY.md	3 years ago
Louis Lam	e1eeb44e7f	Update SECURITY.md	3 years ago
Adam Stachowicz	521d57c483	Fix some of markdownlint warnings	3 years ago
Louis Lam	d6753b8833	Update SECURITY.md	3 years ago
Louis Lam	93a021d027	Update SECURITY.md	3 years ago
LouisLam	3d30ed3d3b	update security policy	3 years ago
Louis Lam	76348cae5d	Update SECURITY.md	3 years ago
Louis Lam	0b32adadb8	Update SECURITY.md	3 years ago
Ziding Zhang	3425a27a0e	Update SECURITY.md ... I'd like to report a security issue and felt it most prudent not to disclose it publicly, as per your Security policy instructions. If not a hassle, might you kindly add an email, or other private contact method? GitHub [recommends](https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository) 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!	3 years ago
Louis Lam	2d36f4cd4a	Create SECURITY.md	3 years ago