Skip to content

Commit a7610db

Browse files
committed
Update security policy guidelines
This is the latest version from our template repo.
1 parent 850b62e commit a7610db

File tree

2 files changed

+16
-10
lines changed

2 files changed

+16
-10
lines changed

.github/SECURITY.md

Lines changed: 16 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,25 @@
11
# Reporting security issues
22

3-
The ReCirq developers and community take security bugs in ReCirq seriously.
4-
We appreciate your efforts to responsibly disclose your findings, and will make
5-
every effort to acknowledge your contributions.
3+
This project's developers and community are committed to addressing security
4+
bugs promptly and effectively. We appreciate your efforts to disclose your
5+
findings responsibly, and will make every effort to acknowledge your
6+
contributions.
67

78
Please **do not** use GitHub issues to report security vulnerabilities; GitHub
89
issues are public, and doing so could allow someone to exploit the information
9-
before the problem can be addressed. Instead, please use the GitHub ["Report
10-
a Vulnerability"](https://github.com/quantumlib/recirq/security/advisories/new)
11-
interface from the _Security_ tab of the ReCirq repository.
10+
before the problem can be addressed. Instead, please use the *Report a
11+
vulnerability* interface from the *Security* tab at the top of this GitHub
12+
repository page.
13+
14+
<div align="center">
15+
<img width="75%" alt="Location of the report button on the repository page"
16+
src="./report-vulnerability-button.png">
17+
</div>
1218

1319
Please report security issues in third-party modules to the person or team
14-
maintaining the module rather than the project stewards, unless you
15-
believe that some action needs to be taken with ReCirq in order to guard
16-
against the effects of a security vulnerability in a third-party module.
20+
maintaining the module rather than this project's stewards, unless you believe
21+
that some action needs to be taken specifically with this project in order to
22+
guard against the effects of a security vulnerability in third-party software.
1723

1824
## Responses to security reports
1925

@@ -27,4 +33,4 @@ announcement, and may ask for additional information or guidance.
2733
Please contact the project stewards at Google Quantum AI via email at
2834
[email protected] if you have questions or other concerns. If
2935
for any reason you are uncomfortable reaching out to the project stewards,
30-
please email [email protected].
36+
please email [email protected] instead.
37.5 KB
Loading

0 commit comments

Comments
 (0)