Security
Security Acknowledgements
Researchers who have helped us make Taskstreamer safer through responsible disclosure.
No acknowledgements yet
About this page
When a researcher reports a security issue under our Vulnerability Disclosure Policy and the report leads to a fix, we credit them here if they want public recognition. Researchers who prefer to stay anonymous are not listed, and that choice is theirs.
We list the date the issue was resolved, the researcher's name or handle of choice, a short description of the class of issue, and a link to a longer writeup where one was published.
Format
- Date
- The date we shipped the fix.
- Researcher
- Name or handle, as the researcher prefers.
- Issue
- A short description of the class of issue (for example, stored XSS in a specific component, or insecure direct object reference in an API endpoint).
- Writeup
- A link to a longer writeup, when one was published. Most entries will not have one.
Acknowledgements
| Date | Researcher | Issue | Writeup |
|---|---|---|---|
| Nobody listed yet We have not had a qualifying report yet. The first researcher who finds a real issue and wants public credit will land at the top of this list. | |||
Want to be the first?
Read the Vulnerability Disclosure Policy for what is in scope and how to report. Then send your finding to security@taskstreamer.com.