CodSpeed · Vulnerability Disclosure

Codspeed Vulnerability Disclosure

Vulnerability disclosure

CodSpeed runs a coordinated vulnerability disclosure program on Hackerone. A dedicated security contact is published.

CompanyPerformanceBenchmarkingContinuous IntegrationDeveloper ToolsObservabilityTestingDevOpsArtificial IntelligenceMCP
Program: Hackerone

Disclosure Policy

Policy

Security Contact

Contact
support@codspeed.io

Source

Vulnerability Disclosure

codspeed-vulnerability-disclosure.yml Raw ↑
generated: '2026-07-18'
method: searched
source: https://codspeed.io/docs/security
policy:
  - https://codspeed.io/docs/security
contact:
  - support@codspeed.io
bug_bounty: none
notes: >-
  No RFC 9116 /.well-known/security.txt and no formal bug-bounty program
  (HackerOne/Bugcrowd/Intigriti) were found. CodSpeed publishes a security
  policy page documenting its practices, GitHub permission model, and a security
  contact. Reported vulnerabilities can be sent to support@codspeed.io.
evidence:
  - source: https://codspeed.io/docs/security
    kind: security-policy-page
  - source: https://trust.codspeed.io
    kind: trust-center

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/codspeed-vulnerability-disclosure"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.