TypeSafe AI · Vulnerability Disclosure

Typesafe Ai Vulnerability Disclosure

Vulnerability disclosure

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

Artificial IntelligenceMachine LearningClassificationContent ModerationDecision SupportStructured OutputsInferenceLLM AlternativeAgent SkillsMCPAgent-NativeDeveloper ToolsA2A
Program: Hackerone

Disclosure Policy

Policy
Policy
Policy

Security Contact

Contact
mailto:security@typesafe.ai

Source

Vulnerability Disclosure

Raw ↑
generated: '2026-09-19'
method: probed
source: https://console.typesafe.ai/.well-known/security.txt
checked: '2026-09-19'
summary: >-
  TypeSafe serves a valid, unexpired RFC 9116 security.txt naming a dedicated security address and a
  PGP key. It does NOT publish a disclosure policy, a safe-harbour statement, a bug bounty, or a
  scope/out-of-scope list — so there is a way to reach the security team and no published process
  once you do.
published: true
rfc9116:
  served: true
  url: https://console.typesafe.ai/.well-known/security.txt
  file: ../well-known/typesafe-ai-security.txt
  status: 200
  expires: '2027-02-26T00:00:00.000Z'
  expired: false
  fields_present: [Contact, Encryption, Expires, Canonical, Preferred-Languages]
  fields_absent: [Policy, Acknowledgments, Hiring, CSAF]
  host_note: >-
    Served ONLY on console.typesafe.ai. https://typesafe.ai/.well-known/security.txt and
    https://api.typesafe.ai/.well-known/security.txt both 404, which is where a researcher looks
    first. The Canonical field correctly names the console host, but the registrable domain does
    not redirect or duplicate it.
contact:
- mailto:security@typesafe.ai
encryption:
- https://console.typesafe.ai/.well-known/pgp-key.asc
preferred_languages: [en]
policy:
  published: false
  url: null
  note: >-
    No Policy: field in the security.txt and no /security, /security/disclosure, /trust or
    /vulnerability-disclosure page on typesafe.ai (all 404). A reporter gets an address and a PGP
    key but no stated response time, no safe harbour, and no in-scope/out-of-scope definition.
bug_bounty:
  published: false
  platforms_checked: [HackerOne, Bugcrowd, Intigriti]
  result: none found
safe_harbour:
  published: false
trust_center:
  present: true
  url: https://trust.typesafe.ai/
  artifact: security/typesafe-ai-trust-center.yml
evidence:
- url: https://console.typesafe.ai/.well-known/security.txt
  status: 200
  content_type: text/plain; charset=UTF-8
  bytes: 223
- url: https://typesafe.ai/.well-known/security.txt
  status: 404
- url: https://api.typesafe.ai/.well-known/security.txt
  status: 404
- url: https://docs.typesafe.ai/.well-known/security.txt
  status: 404
- url: https://typesafe.ai/security
  status: 404

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/typesafe-ai-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.