Bugcrowd
New Organization Roles for Assets and Savant Pathseeker (2026-11-02) commercialThe section your link pointed to isn't on Bugcrowd's page any more, so we've brought you to the top.
Bugcrowd is a crowdsourced security platform that connects organizations with ethical hackers to find and report vulnerabilities through bug bounty and penetration testing programs.
curl -X POST https://api.bugcrowd.com/scan_configurations/{id}/scan_executions \
-H 'Authorization: Token <api_token>' \
-H 'Content-Type: application/json' \
-d '{"trigger_source": "github-actions"}'
Summary
Bugcrowd is a commercial crowdsourced security platform that connects organizations with independent researchers to find vulnerabilities, alongside newer autonomous scanning products for the same purpose. It runs as a SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. platform with customer, researcher, and API docs for integrating findings and credentials into existing workflows, and it is aimed at application owners, security teams, and compliance stakeholders who need vulnerability visibility and reporting rather than at researchers working alone. Its scope spans traditional bug bounty and pentest coordination, classification detail down to things like KerberosKerberosA network authentication protocol that uses tickets issued by a trusted service. Users and services can prove their identities without sending a password to each application. and SCCM abuse paths, and FedRAMPFedRAMPA US government program that standardizes cloud security authorization, letting vendors get a single assessment accepted across federal agencies instead of repeating the process for each one. support for government use, while its Savant Vista and Pathseeker products add autonomous asset discovery and authenticated penetration testing that push validated findings into the same triage inbox.
Bugcrowd is a crowdsourced security platform that connects organizations with ethical hackers to find and report vulnerabilities through bug bounty and penetration testing programs.
How Bugcrowd helps
What unknown assets in my estate have never been through a pentest?
Savant Vista's autonomous discovery maps the estate and Pathseeker launches authenticated penetration tests against what it finds, pushing validated findings into the same Security Inbox as researcher-submitted reports
Has anything changed on my attack surface since the last scan?
a baseline can be established as a known-good state, and subsequent autonomous scans are compared against it to surface newly discovered assets or drift
Can my researchers test the parts of my application that sit behind a login?
authenticated testing supports external identity providers, so autonomous test runs can reach functionality that only appears once a session is established
Which internal attack paths does a given finding actually represent?
findings are classified against the VRT, now including distinct Kerberos, SCCM, and Active Directory misconfiguration categories, so a report maps to a specific abuse path rather than a generic bucket
How severe is a server misconfiguration or SSRF finding once it's reported?
the VRT rates server security misconfigurations across the full P1–P5 spectrum and scores SSRF findings with granular metrics rather than one coarse category
Which researcher requests are still waiting on my team, and for how long?
the inbox filters show active versus resolved Requests a Response, and each request displays the date it was raised so an outstanding one can be tracked by age
Languages
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Bugcrowd, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Bugcrowd puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
bugcrowd.com, every changeBugcrowd's home page and 19 more pages as they looked each month from September 2021 to October 2026: 32 renders, 3 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
32 entries
No entries match these filters.
- November 20261
- October 20263
- September 20267
- August 202615
- July 20264
- May 20261
- April 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.