Lato · Vulnerability Disclosure

Lato Vulnerability Disclosure

Vulnerability disclosure

Lato runs a coordinated vulnerability disclosure program on Hackerone. A machine-readable /.well-known/security.txt is served. A dedicated security contact is published.

CompanyArtificial IntelligenceAgentsMarket ResearchDue DiligenceInvestmentVenture CapitalPrivate EquitySimulationVoice
Program: Hackerone security.txt present

Disclosure Policy

Policy
https://latolabs.io/security

Security Contact

Contact
mailto:security@latolabs.io

Source

Vulnerability Disclosure

lato-vulnerability-disclosure.yml Raw ↑ 
generated: '2026-07-19'
method: searched
probe: true
source: https://www.latolabs.io/.well-known/security.txt
policy:
- https://latolabs.io/security
contact:
- mailto:security@latolabs.io
preferred_languages:
- en
expires: '2027-06-01T00:00:00.000Z'
canonical: https://latolabs.io/.well-known/security.txt
bug_bounty: null
evidence:
- source: well-known/lato-security.txt
  kind: security.txt
  status: 200
  fields:
  - Contact
  - Policy
  - Expires
  - Preferred-Languages
  - Canonical
- source: https://www.latolabs.io/security
  kind: policy-page
  status: 200
  note: >-
    The Policy URL resolves but currently renders only a pointer back to the
    homepage security anchor; no detailed disclosure procedure is published yet.
notes: >-
  Lato publishes a valid RFC 9116 security.txt with a dedicated security@ contact
  and a non-expired Expires field. No public bug bounty program (HackerOne,
  Bugcrowd, Intigriti) was found, and probe-security-programs.py found no trust
  center. No named certifications (SOC 2, ISO 27001, PCI DSS, HIPAA, FedRAMP) are
  published, so no trust-center artifact was written and no Compliance pointer
  was emitted.