Built Robotics · Vulnerability Disclosure

Built Robotics Vulnerability Disclosure

Vulnerability disclosure

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

CompanyRoboticsConstructionAutonomous SystemsHeavy EquipmentSolar EnergyArtificial IntelligenceIndustrial Automation
Program: Hackerone security.txt present

Disclosure Policy

Policy
https://www.builtrobotics.com/security-policy

Security Contact

Contact
erol@builtrobotics.com

Source

Vulnerability Disclosure

built-robotics-vulnerability-disclosure.yml Raw ↑ 
generated: '2026-08-01'
method: searched
probe: true
source: https://www.builtrobotics.com/.well-known/security.txt
policy:
- https://www.builtrobotics.com/security-policy
contact:
- erol@builtrobotics.com
acknowledgements:
- https://www.builtrobotics.com/hall-of-fame
encryption:
- url: https://www.builtrobotics.com/pgp-key.txt
  status: 404
  note: advertised OpenPGP key URL is dead
expiration: '2026-08-01T05:07:51-07:00'
expiration_status: expired-or-expiring-on-probe-date
bug_bounty: none found (no HackerOne, Bugcrowd or Intigriti program located)
evidence:
- source: well-known/built-robotics-security.txt
  kind: security.txt
  http_status: 200
  fetched: '2026-08-01'
caveats:
- >-
  The Policy and Acknowledgements pages could not be independently verified: all HTML
  paths on www.builtrobotics.com return HTTP 403 behind a Cloudflare bot challenge.
  Both URLs are asserted by the provider's own RFC 9116 security.txt.
- >-
  The security.txt Expiration timestamp is at/past the probe date, so the document is
  stale under RFC 9116 section 2.5.5.