Skip to content

docs(security): align the policy with the published one #88

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
deanzaka merged 2 commits into from
Sep 20, 2026
Merged

docs(security): align the policy with the published one #88

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8edb932
docs(security): align the policy with the published one
zakataskade Sep 20, 2026
84d913b
docs(security): keep the investigation-requirements caveat
zakataskade Sep 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,17 @@
**Please report security issues privately — do not open a public issue or PR.**

- Preferred: open a [GitHub private security advisory](https://github.com/taskade/mcp/security/advisories/new) (Security → Report a vulnerability).
- Or email [hello@taskade.com](mailto:hello@taskade.com) with details and reproduction steps.
- Or email [support@taskade.com](mailto:support@taskade.com) with details and reproduction steps.

We aim to acknowledge reports within **3 business days** and to provide a remediation
timeline after triage. Please give us a reasonable window to ship a fix before any
public disclosure. We're happy to credit reporters who request it.
We are a small team and do not guarantee a response time. Reports go to a monitored
mailbox and are routed to engineering, and complex reports take longer to triage. We
aim for 90-day coordinated disclosure when feasible, subject to investigation
requirements, so please give us a reasonable window to ship a fix before going public.
On request we credit you by name once a fix ships. We do not run a bug bounty program
and do not pay for vulnerability reports.

The full policy is published at [taskade.com/security](https://www.taskade.com/security),
and it is the one that applies if it and this file ever disagree.

## Token Handling

Expand Down
Loading