HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
propublica
compas-analysis
Jupyter Notebook2016–2016
propublica / compas-analysis

compas-analysis

Data and analysis for 'Machine Bias'

2Distinct people
6Mentions
0Explicit recommenders
701GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Data and analysis for 'Machine Bias'

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week6 dated mentions

Observed mentions: 2016-05-23 18:51:11 UTC to 2016-06-29 17:20:59 UTC. Weeks start Monday, UTC.

0123452016-05-23 00:00:00 UTC to 2016-05-30 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 commentsMay 232016-05-30 00:00:00 UTC to 2016-06-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-06 00:00:00 UTC to 2016-06-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 62016-06-13 00:00:00 UTC to 2016-06-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-20 00:00:00 UTC to 2016-06-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-27 00:00:00 UTC to 2016-07-04 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 27

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 232016-05-23 00:00:00 UTC2016-05-30 00:00:00 UTC505
May 302016-05-30 00:00:00 UTC2016-06-06 00:00:00 UTC000
Jun 62016-06-06 00:00:00 UTC2016-06-13 00:00:00 UTC000
Jun 132016-06-13 00:00:00 UTC2016-06-20 00:00:00 UTC000
Jun 202016-06-20 00:00:00 UTC2016-06-27 00:00:00 UTC000
Jun 272016-06-27 00:00:00 UTC2016-07-04 00:00:00 UTC101

What Hacker News says

6 sources
Go read the description of the statistical analysis or just view their R notebook: https://github.com/propublica/compas-analysis/blob/master/Co... Their own analysis shows that (p ~= 0) that high and medium risk factors are predictive. They also showed that the racial bias terms (race_factorAfrican-American:score_factorHigh, etc) are probably not predictive (p > 0.05). Your quotes are not evidence of bias, though I see how they might confuse an innumerate reader. It's interesting how good a job this article is doing confusing the innumerate - it's almost as if it was written to mislead without technically lying. For example, black defendants being pegged as being more likely to commit crimes can be caused by one of two things: bias or perhaps black defends actually are more likely to commit crimes. According to ProPublica's own analysis (
Read the rest
see race_factorAfrican-American), the latter is actually the case. This is true with p = 4.52e-06 - see line [36].
In Machine Bias
The validity of the algorithm can be - and apparently has been - reliably tested and been found to be useful and mostly unbiased. This analysis has been performed by both the algorithm's creators and highly adversarial third parties, such as the author of this article. Both found that whatever bias there is is small, and cannot be distinguished from random chance. For example, the author of this very article has done such an analysis. Here's her R notebook: https://github.com/propublica/compas-analysis/blob/master/Co... Her analysis shows (within the limitations of the frequentist paradigm) that: a) the predictor is useful - score_factorHigh and score_factorMedium both have p-values that are essentially zero. b) The predictor is not racially biased that much - race_factorAfrican-American:score_factorHigh and the other bias terms have p-va
Read the rest
lues that are > 0.05 . Look, I'd love it if we required such algorithms to be open source. I'm a huge proponent of both open science and open government. Nevertheless, there is an entire discipline devoted to evaluating predictive algorithms without needing to care about their details - it's called "machine learning". The wonderful thing about statistics is that even a highly biased person (such as the author of this article) can still reach a correct conclusion that goes against their biases.
In Machine Bias
According to propublicas own analysis, the claim of bias cannot be shown to be statistically significant. https://www.propublica.org/article/how-we-analyzed-the-compa... This article is terrible data journalism and probably deliberately misleading. Step 1: write down conclusion. Step 2: do analysis. Step 3: if analysis doesn't support conclusion, write down a bunch of anecdotes. Really, here's her R script: https://github.com/propublica/compas-analysis/blob/master/Co... Just read that. It's vastly better than this nonsensical article.
In Machine Bias

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.