Liquidtrust Vulnerability Disclosure

generated: '2026-07-19'
method: searched
probe: true
source: https://www.liquidtrust.io/security
policy:
- https://www.liquidtrust.io/security
contact:
- support@liquidtrust.io
- https://www.liquidtrust.io/contact
program:
  type: responsible-disclosure
  bug_bounty: false
  platform: null
  intake: >-
    A "Report a Vulnerability" link on the security page routes to the general contact form at
    https://www.liquidtrust.io/contact. There is no dedicated security@ address published and no
    third-party bug bounty platform (HackerOne, Bugcrowd, Intigriti) is referenced.
  commitment: >-
    The security page states LiquidTrust welcomes reports from security researchers, acknowledges
    reports "in a timely manner", and works to address valid concerns. No published response-time SLA,
    safe-harbor language, or reward schedule.
security_txt:
  present: false
  evidence: >-
    /.well-known/security.txt returns 404 on liquidtrust.io, www.liquidtrust.io, and
    api.liquidtrust.io (probed 2026-07-19). RFC 9116 is not implemented.
evidence:
- source: https://www.liquidtrust.io/security
  kind: disclosure page
  keywords:
  - vulnerability
  - responsible disclosure
  - security research
  - security issue
gaps:
- No /.well-known/security.txt (RFC 9116)
- No dedicated security@ contact address
- No safe-harbor statement or published response SLA
- No bug bounty program
see_also: security/liquidtrust-trust-center.yml