Supaglue · Vulnerability Disclosure

Supaglue Vulnerability Disclosure

Vulnerability disclosure

Supaglue publishes a vulnerability disclosure policy for reporting security issues. A machine-readable /.well-known/security.txt is served. A dedicated security contact is published.

CRMHRISUnified-APIOpen-SourceIntegrationSales EngagementTicketingData SynchronizationMarketing AutomationEnrichmentWebhookArchived

Program: security.txt present

Disclosure Policy

Policy

https://github.com/supaglue-labs/supaglue/blob/main/SECURITY.md

Policy

https://github.com/supaglue-labs/supaglue/blob/main/docs/docs/security_legal/security.md

Security Contact

Contact

security@supaglue.com

Contact

hello@supaglue.com

Source

Vulnerability Disclosure

generated: '2026-08-13'
method: searched
probe: true
source: https://github.com/supaglue-labs/supaglue/blob/main/SECURITY.md
status: published-but-unreachable
note: >-
  Supaglue published a real security policy — a SECURITY.md in the root of its repository, plus a
  "How to report vulnerabilities" section on its security page — and both documents are still live
  and readable on GitHub. Neither contact still works: security@supaglue.com and hello@supaglue.com
  sit on supaglue.com, which now redirects to a HugeDomains sale listing, so the mailbox is no longer
  the company's. There is no security.txt (every /.well-known/security.txt probe returns a soft-200
  parking page, and the one that returned text/plain came from an unrelated site that supaglue.io now
  redirects to), and there was never a bug-bounty program.
policy:
  - https://github.com/supaglue-labs/supaglue/blob/main/SECURITY.md
  - https://github.com/supaglue-labs/supaglue/blob/main/docs/docs/security_legal/security.md
contact:
  - security@supaglue.com
  - hello@supaglue.com
contact_status: >-
  Both addresses are on a domain the company no longer controls (supaglue.com 302s to
  hugedomains.com, probed 2026-08-13). Treat them as dead.
bug_bounty: null
supported_versions: >-
  "We recommend using the latest version of Supaglue to ensure you get all security updates." No
  version window is defined, and no security update has shipped since the repository was archived on
  2024-03-10.
evidence:
  - source: https://github.com/supaglue-labs/supaglue/blob/main/SECURITY.md
    kind: SECURITY.md
    http_status: 200
    fetched: '2026-08-13'
  - source: https://www.supaglue.com/.well-known/security.txt
    kind: security.txt probe
    http_status: 200
    fetched: '2026-08-13'
    note: soft-200 — HTML domain-sale page, no security.txt served
  - source: https://api.supaglue.io/.well-known/security.txt
    kind: security.txt probe
    http_status: 0
    fetched: '2026-08-13'
    note: host does not resolve
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/supaglue-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.

GitHub Google LinkedIn

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