Connectors built by other CMDash customers
When a workspace builds a custom connector for a tool CMDash does not ship an adapter for, they can submit it. CMDash reviews it, publishes it here, and any workspace can install it against their own credentials.
A connector definition is data, never code
What gets shared is an HTTP request template and a list of JSONPath field mappings — the same declarative shape you would author by hand in CMDash. Nothing executable ever crosses between workspaces, and no credential does either: installing a community connector copies the definition and asks you for your own key, which stays encrypted in your workspace and is never shared back to the contributor.
Every template here was reviewed by CMDash and carries a SHA-256 checksum of the exact content that was reviewed. That supports one claim — this byte content was reviewed on that date — and is not a signature or a statement about who wrote it.
No community connectors have been published yet
The programme is open and the review queue is live — nothing has cleared review yet. If you have built a custom connector inside CMDash, submit it from the Custom Connectors page and it will appear here once it is reviewed. In the meantime, the 47 adapters CMDash ships cover most EDR, vulnerability, cloud, SIEM, identity and ticketing stacks.
Submitting one of your own
Build the connector in your workspace first — Integrations → Custom connectors → New — and once it is syncing, use “Submit as template”. CMDash reviews the request template and the field mappings before anything is published; a submission stays private to your workspace until it is.
Nothing about your workspace travels with a submission: the published template carries the name, description, category, credential type and field mappings, and no identifier for the organization that contributed it.