jj/SECURITY.md

To report a security issue, please
email Jujutsu VCS Security at <jj-security@googlegroups.com>
with a description of the issue, the steps you took to create the issue,
affected versions, and, if known, mitigations for the issue. Our vulnerability
management team will respond within 3 working days of your email. If the issue
is confirmed as a vulnerability, we will open a Security Advisory. This project
follows a 90 day disclosure timeline.
docs: add a SECURITY.md I've set up a jj-security@googlegroups.com list. The template comes from Google's internal web. I have no experience with GitHub's Security Advisory database, but it seems like a good practice, so let's use it. 2023-03-10 21:59:37 +03:00			`To report a security issue, please`
SECURITY.md: show the email plainly Previously, the link wasn't working from Github's rendered markdown. Another alternative is to add `malto:` to the link, which would make it work. However, I thought that since the email is the most important piece of information in the entire file, we should just write it out. 2023-06-04 08:05:53 +03:00			`email Jujutsu VCS Security at <jj-security@googlegroups.com>`
docs: add a SECURITY.md I've set up a jj-security@googlegroups.com list. The template comes from Google's internal web. I have no experience with GitHub's Security Advisory database, but it seems like a good practice, so let's use it. 2023-03-10 21:59:37 +03:00			`with a description of the issue, the steps you took to create the issue,`
			`affected versions, and, if known, mitigations for the issue. Our vulnerability`
			`management team will respond within 3 working days of your email. If the issue`
			`is confirmed as a vulnerability, we will open a Security Advisory. This project`
			`follows a 90 day disclosure timeline.`