Skip to content
Make AI Good

Graph · Publication

Bug Bounties For Algorithmic Harms?

01 · In focus

One publication, in the field.

The structured facts the source records about Bug Bounties For Algorithmic Harms?, the count of declared adjacencies in the corpus, and the federation map zoomed on this node and its neighbours.

publication

4 declared connections

Kind
Publication
Status
active
Confidence
high
Type
report
Date
2022-01-27
Entity ID
pub-bug-bounties-for-algorithmic-harms
Network
View in network

Tags report, ajl, crash-project, algorithmic-harms, bug-bounties, vulnerability-disclosure, algorithmic-accountability, participatory-audit, community-reporting, evocative-audit, twitter-bias-bounty, design-framework, foundational-artefact

Bug Bounties For Algorithmic Harms? · 4 direct neighbours visible

02 · Connections

4 adjacencies, by relation.

Split by direction. Direct links are the ones Bug Bounties For Algorithmic Harms?’s source record names; inferred backlinks are records elsewhere in the corpus that point at this entity.

Direct from this record

3 links

Links named in this entity's structured fields.

Inferred backlinks

1 link

Other records that name this entity.

03 · Background

From the source record.

Body prose as it appears in movement-graph’s published markdown for this entity. Links to other corpus entities resolve to their graph page; links to deeper repo paths are kept as text so the page does not invent a route.

Bug Bounties For Algorithmic Harms? Lessons from Cybersecurity Vulnerability Disclosure for Algorithmic Harms Discovery, Disclosure, and Redress is a report published by the Algorithmic Justice League on 27 January 2022 and authored by Josh Kenway, Camille François, Sasha Costanza-Chock, Inioluwa Deborah Raji, and Joy Buolamwini. The report is the foundational publication of AJL's Community Reporting of Algorithmic System Harms (CRASH) project — originally launched in July 2020 as the Algorithmic Vulnerability Bounty Project — and asks whether the bug-bounty model that the cybersecurity field developed for paying outside researchers to find and disclose security vulnerabilities can be adapted to the discovery, disclosure, and redress of algorithmic harms.

The report opens from the observation that bug-bounty programmes (BBPs) — once a contested practice — are now a routine part of how Google, the U.S. Department of Defense, Starbucks, and hundreds of other organisations buy security flaws from outside researchers, and that a small number of operators (Rockstar Games, Twitter, and others) had begun by 2022 to extend the BBP frame to socio-technical issues including algorithmic bias and content-moderation harms. The authors draw on interviews with BBP experts and practitioners, a literature review, and a case study of Twitter's 2021 algorithmic-bias bounty pilot to set out a design framework for what BBPs would have to look like in order to surface algorithmic harms rather than only security flaws. The five summary takeaways — reproduced in the report's launch coverage — call on operators to prepare BBPs to include socio-technical concerns rather than treating algorithmic harms as bolt-ons to a security programme; to look across the lifecycle of an AI system, accompanying BBPs with other accountability mechanisms; to nurture a community of practice that does not exclude non-computer-scientists; to intentionally develop a diverse, inclusive community of researchers and community advocates with fair compensation; and to foster and protect participatory adversarial research with a guarantee of public disclosure of findings. The report's recommendations sit alongside pre-publication public framings by AJL researchers that argued for adapting the bug-bounty model specifically to biometric algorithm bias.

Within the corpus, Bug Bounties For Algorithmic Harms? is the third Algorithmic Justice League-anchored Publication after Unmasking AI and Comply To Fly?, and the second AJL-as-publisher artefact in the corpus exercising publisher: org-algorithmic-justice-league after Comply To Fly?. The report sits earliest in time of the three AJL Publications and provides the design framework that the Freedom Flyers participatory-audit campaign and the Comply To Fly? report later put into practice at scale: where Comply To Fly? applies AJL's evocative-audit method to a single federal facial-recognition deployment, Bug Bounties For Algorithmic Harms? sets out the broader institutional question of how outside researchers and affected communities can be brought into the harms-discovery process at all. The MacArthur Foundation's grantee-publications page for the report records AJL's grantee status under the Foundation's Technology in the Public Interest programme, and the report's published acknowledgements (carried in the AJL landing page and the report PDF) credit the Alfred P. Sloan Foundation, the Rockefeller Foundation, and the Mozilla Foundation as supporting funders. The report has since been a frequent reference point in subsequent AJL programme work and in adjacent academic and policy writing on algorithmic auditing, participatory audit, and community reporting of AI harms.

04 · Sources

Where this came from.

8 sources listed from the pinned corpus. Links are shown only when the source URL is a valid HTTP(S) address.

  1. ajl.org

    Checked 2026-05-09

    report's own landing page on the Algorithmic Justice League site — primary source for the report's title, framing, and CRASH-project anchoring

  2. aihub.org

    Checked 2026-05-09

    AIhub coverage of the report's release with the report's own formal citation reproduced ("Kenway, Josh, Camille François, Sasha Costanza-Chock, Inioluwa Deborah Raji, and Joy Buolamwini. Bug Bounties For Algorithmic Harms? Lessons from Cybersecurity Vulnerability Disclosure for Algorithmic Harms Discovery, Disclosure, and Redress. Washington, DC: Algorithmic Justice League. January 2022.") — primary source for the full author list, the report's full subtitle, and the five summary takeaways

  3. mediawell.ssrc.org

    Checked 2026-05-09

    Social Science Research Council MediaWell entry for the report — primary source for the 27 January 2022 publication date attribution

  4. drive.google.com

    Checked 2026-05-09

    Google-Drive-hosted PDF of the full report, linked from the AJL landing page and AIhub coverage

  5. assets.website-files.com

    Checked 2026-05-09

    AJL Webflow asset hosting of the full report PDF — alternative primary text

  6. macfound.org

    Checked 2026-05-09

    MacArthur Foundation grantee-publications page for the report (4 February 2022) — primary source for AJL's grantee status under the Foundation's Technology in the Public Interest programme and for the funder-side framing of the report's policy contribution

  7. ajl.org

    Checked 2026-05-09

    AJL Community Reporting of Algorithmic System Harms (CRASH) project page — primary source for the report's positioning as the foundational artefact of the CRASH project (originally the Algorithmic Vulnerability Bounty Project)

  8. biometricupdate.com

    Checked 2026-05-09

    Biometric Update coverage from March 2021 of the project's pre-publication framing — primary source for the project's near-year-long pre-publication public phase ahead of the January 2022 report

Source: entities/publications/pub-bug-bounties-for-algorithmic-harms.md in movement-graph at pin 3cc1a36.