About Swarm Research Labs

A hive that shows its work.

Software is written faster than anyone can review it. We build the reader that keeps up.

The story

The future showed up early.

On 14 October 2026, a swarm of 677 hunters, sized for the codebase, took on Grafana 8.3.0 — 6,587 files, nearly one million lines — and came back in under 17 minutes with 13 confirmed vulnerabilities. Two had never been named in any advisory.

Nobody told it where to look. The case study has every finding.

The mission

Make software far more secure.

Real vulnerabilities sit in code nobody had the hours to read. A reader that never tires changes that.

We want every project, from a lone maintainer's library to a platform's monorepo, read in full by something that answers to the code alone.

How we behave

How we work.

Independence

We don't sell the models.

An auditor with a model to sell has a reason to find that model fine. We have none, so the audit has one job: find what is true about your code.

HunterSwarm runs today, as a service we operate. Dedicated and government arrangements, by conversation.

Contact

A person reads it.

Five addresses, one job each

Write to the one that fits. Security reports are read first.

Helpsupport@hunterswarm.comSomething doesn't work, or a result looks wrong. Include the finding id and the commit.
Securitysecurity@hunterswarm.comA problem in HunterSwarm itself. For the flaws the swarm finds in other people's code, see how we disclose.
Briefingssales@hunterswarm.comSee the swarm on your own code. Request a briefing.
Presspress@hunterswarm.comFor anything a story needs.
Everything elsehello@hunterswarm.comAnything that isn't above.

What your attackers would find, the swarm finds first.