generated: '2026-08-25'
method: probed
source: >-
  Anonymous probes of Logiwa's own hosts plus the HackerOne and Bugcrowd program directories.
name: Logiwa vulnerability disclosure
description: >-
  RECORDED ABSENCE. Logiwa publishes no vulnerability disclosure policy, no security contact and
  no bug bounty program that an anonymous researcher can find. No Security pointer is claimed in
  apis.yml, because there is no disclosure surface to point at.
policy_published: false
security_txt: false
bug_bounty: false
security_contact: null
probes:
- url: https://www.logiwa.com/.well-known/security.txt
  http_status: 404
- url: https://www.logiwa.com/security.txt
  http_status: 404
- url: https://developer.logiwa.com/.well-known/security.txt
  http_status: 404
- url: https://app.logiwa.com/.well-known/security.txt
  http_status: 404
- url: https://appapi.logiwa.com/.well-known/security.txt
  http_status: 401
- url: https://www.logiwa.com/vulnerability-disclosure
  http_status: 404
- url: https://www.logiwa.com/responsible-disclosure
  http_status: 404
- url: https://www.logiwa.com/security-policy
  http_status: 404
- url: https://www.logiwa.com/company/security
  http_status: 404
- url: https://hackerone.com/logiwa
  http_status: 404
- url: https://bugcrowd.com/logiwa
  http_status: 404
note: >-
  The Vanta Trust Center at https://trust.logiwa.com may carry a security contact behind its
  request flow, but nothing is reachable anonymously. A researcher's only published route is the
  general https://www.logiwa.com/contact-us form.
findings:
- id: no-security-txt
  severity: medium
  detail: >-
    RFC 9116 security.txt is absent on every Logiwa host. A researcher who finds a vulnerability
    in a system holding warehouse inventory and order data for many 3PL client brands has no
    published disclosure channel.
x-evidence:
  fetched: '2026-08-25'