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.
- Show the work. Every finding carries its file, its exact lines and its trace. If we can't show you the line, it isn't a finding.
- Your findings are yours. They go to you, and we never publish them without your consent.
- Maintainers hear first. When we hunt open-source code on our own initiative, what we find goes to its maintainers privately, with time to ship the fix, before anything is published. Work we do for a client follows that client's agreement.
- Describe code, not people. A finding is about a line of code, never about who wrote it.
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.
Write to the one that fits. Security reports are read first.