AxleHire (Jitsu) · Vulnerability Disclosure

Axlehire Vulnerability Disclosure

Vulnerability disclosure

Jitsu (formerly AxleHire) publishes a responsible-disclosure invitation on its security page. There is no RFC 9116 /.well-known/security.txt on any Jitsu host (all probed 404 or answered with an SPA shell), and no bug-bounty program on HackerOne, Bugcrowd or Intigriti was found. Reports are taken by email and through a hosted intake form.

AxleHire (Jitsu) runs a coordinated vulnerability disclosure program on Hackerone.

CompanyLogisticsLast Mile DeliveryShippingParcelTransportationSupply ChainE-CommerceTrackingWebhook
Program: Hackerone

Disclosure Policy

Security Contact

Source

Vulnerability Disclosure

Raw ↑
generated: '2026-08-06'
method: searched
probe: true
source: https://gojitsu.com/security
description: >-
  Jitsu (formerly AxleHire) publishes a responsible-disclosure invitation on its
  security page. There is no RFC 9116 /.well-known/security.txt on any Jitsu
  host (all probed 404 or answered with an SPA shell), and no bug-bounty program
  on HackerOne, Bugcrowd or Intigriti was found. Reports are taken by email and
  through a hosted intake form.
program:
  type: responsible-disclosure
  bug_bounty: false
  safe_harbor_stated: false
  policy_url: https://gojitsu.com/security
  contact_email: support@gojitsu.com
  report_forms:
  - https://j-it.su/rd
  - https://docs.google.com/forms/d/e/1FAIpQLSeDO_UZC0rOSWOCwka3XLMdeucpS3u8kyTpmUKYE7u7BuU63g/viewform
  guidance: >-
    "If you discover a potential security vulnerability in our systems, we
    encourage you to report it to us promptly and responsibly" — reporters are
    asked to avoid accessing, modifying or deleting data and to allow a
    reasonable remediation window.
  trust_center: https://trust.gojitsu.com/
security_txt:
  published: false
  probed:
  - url: https://gojitsu.com/.well-known/security.txt
    status: 404
  - url: https://api.gojitsu.com/.well-known/security.txt
    status: 404
  - url: https://docs.gojitsu.com/.well-known/security.txt
    status: 200
    note: >-
      Firebase SPA catch-all — returns the docs index.html (text/html) for every
      /.well-known/* path. Not a real security.txt.
x-evidence:
  fetched: '2026-08-06'
  url: https://gojitsu.com/security
  http_status: 200
  control_path_status: 404
  control_note: >-
    https://gojitsu.com/this-page-does-not-exist-control returns 404 with a
    22076-byte HubSpot 404 body, so the 25876-byte 200 at /security is a real
    page and not a soft-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/axlehire-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 email required.

A second provider on the same verified email joins the account you already have.