You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SECURITY.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,7 @@
4
4
5
5
**Do not open a public GitHub issue for security vulnerabilities.**
6
6
7
-
Report privately through either channel:
8
-
9
-
-**GitHub Private Vulnerability Reporting** (preferred): [Report a vulnerability](https://github.com/ionq/ionq-core-python/security/advisories/new). The report is visible only to repository maintainers and people you invite to the advisory.
10
-
-**Email**: [security@ionq.co](mailto:security@ionq.co) with the subject line `[ionq-core-python]`.
7
+
Email [security@ionq.co](mailto:security@ionq.co) with the subject line `[ionq-core-python]`.
11
8
12
9
Please include enough detail to reproduce the issue, and redact your API key from any logs or response payloads you share.
13
10
@@ -25,7 +22,7 @@ When conducting security research consistent with this policy, we consider your
25
22
- We will not bring a claim against you for circumvention of technical controls under relevant anti-circumvention laws (such as DMCA section 1201).
26
23
- If a third party initiates legal action against you for activities conducted in good-faith compliance with this policy, we will take steps to make it known that your actions were authorized.
27
24
28
-
In return, we ask that you comply with all applicable laws, make reasonable efforts to avoid privacy violations, service disruption, and destruction of data, limit testing to your own account or accounts you control, and use the channels above to discuss vulnerabilities with us.
25
+
In return, we ask that you comply with all applicable laws, make reasonable efforts to avoid privacy violations, service disruption, and destruction of data, limit testing to your own account or accounts you control, and use the email above to discuss vulnerabilities with us.
29
26
30
27
If you are unsure whether a planned activity is consistent with this policy, contact <security@ionq.co> before proceeding. Safe harbor applies only to claims within IonQ's control; this policy does not bind independent third parties.
0 commit comments