security

KO | EN

gitlite — search

#typescript #ai-agents #deepseek-harness #dsh-plugin #open-source #ai #claude-code #cli #windows #codex #developer-tools #dsh

★ 91 Open GitHub ↗

Collection of CVEs from Sick Codes, or collaborations on https://sick.codes security research & advisories.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Sick Codes Security Advisories

## - [View All Advisories](advisories)
## - [Submit a Vulnerability](https://sick.codes/submit-vulnerability/)
## - [Public PGP Key](https://github.com/sickcodes/pgp)
## - [VDP (see below, or external)](https://sick.codes/vdp/) 
# SICK CODES Vulnerability Disclosure Program & Vulnerability Disclosure Policy

[Terms Generated Under CC0-1.0 License using the Disclose.io project terms generator.](https://github.com/disclose/dioterms)

## Introduction

SICK CODES welcomes feedback from security researchers and the general public to help improve global security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any software, hardware, or device, or in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, what you can expect from us.

## Systems in Scope

This policy applies to any digital assets owned, operated, or maintained by SICK CODES, as well as certain digital assets that are particularly interesting or urgent in nature.

## Out of Scope

Vulnerabilities that are already covered by another CNA mya be reported to us, which we will in turn forward to the respective CNA as found on [https://cve.mitre.org/cve/request_id.html](https://cve.mitre.org/cve/request_id.html).

## Our Commitments

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

- Respond to your report within 24 hours, and work with you to understand and validate your report;
- Sometimes engage additional reseachers or analysts to assist in validating your findings;
- Keep you informed at all stages about the progress of a vulnerability as it is processed;
- Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
- Extend Full Safe Harbor for your vulnerability research that is related to this policy.

## Our Expectations

In participating in our 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 as soon as you can;
- Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
- Use only the Official Channels to discuss vulnerability information with us;
- We will usually work diretly with you on your research from the initial report until disclosure to resolve the issue before you disclose it publicly, or if the vulnerability is already public;
- 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.
- Do not engage in blackmail.

## Official Channels

- [https://sick.codes/submit-vulnerability/](https://sick.codes/submit-vulnerability/)
- [https://twitter.com/sickcodes](https://twitter.com/sickcodes)
- [https://keybase.io/sickcodes](https://keybase.io/sickcodes)

Please use any of those channels, or email, to report security issues, providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue.

## Safe Harbor

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.

We will do our very best to protect you, and if you wish to remain anonymous during disclosure, you are more than welcome to make that request.

security

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README