Security Policy

I welcome feedback from security researchers and the general public to help improve this project's security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of the project's assets, I want to hear from you. This policy outlines steps for reporting vulnerabilities to me, what I expect, what you can expect from me.

Our Commitments

When working with me, according to this policy, you can expect me to:

Respond to your report promptly, and work with you to understand and validate your report;
Strive to keep you informed about the progress of a vulnerability as it is processed;
Work to remediate discovered vulnerabilities in a timely manner, within my operational constraints; and
Extend Safe Harbor for your vulnerability research that is related to this policy.

Our Expectations

In participating in the project's vulnerability disclosure program in good faith, we ask that you:

Play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
Report any vulnerability you’ve discovered promptly;
Avoid violating the privacy of others, disrupting the project's systems, destroying data, and/or harming user experience;
Use only the Official Channels to discuss vulnerability information with me;
Provide me a reasonable amount of time (at least 90 days from the initial report) to resolve the issue before you disclose it publicly;
Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
You should only interact with test accounts you own or with explicit permission from the account holder; and
Do not engage in extortion.

Reporting a Vulnerability

To report vulnerabilities please email [email protected] and include:

"SECURITY" in the email subject line
A description of the issue
Steps to reproduce the issue
Affected versions
Suggested mitigation (optional)

Encryption

When possible we recommend using encryption to report serious vulnerabilities. You can find our PGP Public key below and in the project's security.txt file. Please reach out to the contact address if you have any issues or prefer an alternative form of encrypted communication.

PGP Public Key

https://keys.openpgp.org/search?q=9AEC89F0B43B891754292434C0394F55B26FEB90

Safe Harbour

When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:

Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
Authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
Exempt from restrictions in our Terms of Service (TOS) and/or Acceptable Usage Policy (AUP) that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
Lawful, helpful to the overall security of the Internet, and conducted in good faith.

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.

Note that the Safe Harbor applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.

Acknowledgements

Credit to https://github.com/Trewaters/security-README for helpful guidelines on setting up security files on GitHub.
Thanks to https://github.com/securitytxt/ for their work on standardisation.
Thanks to https://github.com/OWASP/ and particularly their Vulnerability Disclosure Cheat Sheet
Thanks to https://github.com/disclose for their Safe Harbour and other terms

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Security

.github/SECURITY.md

Security Policy

Our Commitments

Our Expectations

Reporting a Vulnerability

Encryption

Safe Harbour

Acknowledgements

There aren’t any published security advisories

Security: wmorland/alfred-py3-default-browser

Security

.github/SECURITY.md

Security Policy

Our Commitments

Our Expectations

Reporting a Vulnerability

Encryption

Safe Harbour

Acknowledgements

There aren’t any published security advisories