Edge Impulse · Vulnerability Disclosure

Edge Impulse Vulnerability Disclosure

Vulnerability disclosure

Edge Impulse publishes NO coordinated vulnerability disclosure program. There is no security.txt on any host, no /security/disclosure or /responsible-disclosure page, no first-party SECURITY.md in the GitHub organization (all 73 SECURITY.md hits there are vendored third-party files — ARM Ethos core driver, STMicroelectronics STM32Cube middleware — not Edge Impulse policy), and no HackerOne, Bugcrowd or Intigriti listing. The public security page is a SOC 2 compliance narrative with a Contact Sales button — it names no security contact, no reporting address and no safe-harbour language. A researcher who finds a flaw in the Studio API has no published route to report it. This is the clearest fixable gap in the Edge Impulse security posture; a single RFC 9116 security.txt would close it.

Edge Impulse runs a coordinated vulnerability disclosure program on Hackerone. A dedicated security contact is published.

Artificial IntelligenceMachine LearningEmbedded Machine LearningEdge AIMLOpsComputer VisionInternet of ThingsModel DeploymentDeveloper Tools
Program: Hackerone

Disclosure Policy

Security Contact

Contact
noteThe only published route is the general contact form at https://www.edgeimpulse.com/contact.
Contact
security_email

Source

Vulnerability Disclosure

Raw ↑
generated: '2026-09-06'
method: probed
source: Live probes of /.well-known/security.txt on 7 hosts, https://www.edgeimpulse.com/security, https://github.com/edgeimpulse,
  bug-bounty platform search
provider: Edge Impulse
providerId: edge-impulse
program_published: false
description: Edge Impulse publishes NO coordinated vulnerability disclosure program. There is no security.txt
  on any host, no /security/disclosure or /responsible-disclosure page, no first-party SECURITY.md in
  the GitHub organization (all 73 SECURITY.md hits there are vendored third-party files — ARM Ethos core
  driver, STMicroelectronics STM32Cube middleware — not Edge Impulse policy), and no HackerOne, Bugcrowd
  or Intigriti listing. The public security page is a SOC 2 compliance narrative with a Contact Sales
  button — it names no security contact, no reporting address and no safe-harbour language. A researcher
  who finds a flaw in the Studio API has no published route to report it. This is the clearest fixable
  gap in the Edge Impulse security posture; a single RFC 9116 security.txt would close it.
security_txt:
  served: false
  hosts_probed:
  - edgeimpulse.com
  - www.edgeimpulse.com
  - docs.edgeimpulse.com
  - studio.edgeimpulse.com
  - forum.edgeimpulse.com
  - ingestion.edgeimpulse.com
  - remote-mgmt.edgeimpulse.com
  status: 404
bug_bounty:
  platform: null
  found: false
contact:
  security_email: null
  note: The only published route is the general contact form at https://www.edgeimpulse.com/contact.
evidence:
- url: https://edgeimpulse.com/.well-known/security.txt
  status: 404
- url: https://www.edgeimpulse.com/.well-known/security.txt
  status: 404
- url: https://docs.edgeimpulse.com/.well-known/security.txt
  status: 404
- url: https://studio.edgeimpulse.com/.well-known/security.txt
  status: 404
- url: https://www.edgeimpulse.com/security
  status: 200
  note: SOC 2 compliance page; no disclosure policy, no security contact, no safe harbour.
- url: https://www.edgeimpulse.com/responsible-disclosure
  status: 404
- url: https://hackerone.com/edgeimpulse
  status: 404
- url: https://bugcrowd.com/edgeimpulse
  status: 404
- url: https://github.com/edgeimpulse/.github
  status: 404
  note: No org-level community health repo, so no org-wide SECURITY.md.
related:
  trust_center: security/edge-impulse-trust-center.yml
  well_known: well-known/edge-impulse-well-known.yml
  domain_security: security/edge-impulse-domain-security.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/edge-impulse-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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