HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mit-pdos
fscq
Coq2015–2016
mit-pdos / fscq

fscq

FSCQ is a certified file system written and proven in Coq

3Distinct people
3Mentions
0Explicit recommenders
252GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

FSCQ is a certified file system written and proven in Coq

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:56:07 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 week3 dated mentions

Observed mentions: 2015-11-20 02:14:05 UTC to 2016-05-01 21:37:57 UTC. Weeks start Monday, UTC.

0122015-11-16 00:00:00 UTC to 2015-11-23 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsNov 162015-11-23 00:00:00 UTC to 2015-11-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-30 00:00:00 UTC to 2015-12-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-07 00:00:00 UTC to 2015-12-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-14 00:00:00 UTC to 2015-12-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-21 00:00:00 UTC to 2015-12-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-28 00:00:00 UTC to 2016-01-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-04 00:00:00 UTC to 2016-01-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-11 00:00:00 UTC to 2016-01-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-18 00:00:00 UTC to 2016-01-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-25 00:00:00 UTC to 2016-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-01 00:00:00 UTC to 2016-02-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 12016-02-08 00:00:00 UTC to 2016-02-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-15 00:00:00 UTC to 2016-02-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-22 00:00:00 UTC to 2016-02-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-29 00:00:00 UTC to 2016-03-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-07 00:00:00 UTC to 2016-03-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-14 00:00:00 UTC to 2016-03-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-21 00:00:00 UTC to 2016-03-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-28 00:00:00 UTC to 2016-04-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-04 00:00:00 UTC to 2016-04-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-11 00:00:00 UTC to 2016-04-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-18 00:00:00 UTC to 2016-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-25 00:00:00 UTC to 2016-05-02 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 25

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
Nov 162015-11-16 00:00:00 UTC2015-11-23 00:00:00 UTC202
Nov 232015-11-23 00:00:00 UTC2015-11-30 00:00:00 UTC000
Nov 302015-11-30 00:00:00 UTC2015-12-07 00:00:00 UTC000
Dec 72015-12-07 00:00:00 UTC2015-12-14 00:00:00 UTC000
Dec 142015-12-14 00:00:00 UTC2015-12-21 00:00:00 UTC000
Dec 212015-12-21 00:00:00 UTC2015-12-28 00:00:00 UTC000
Dec 282015-12-28 00:00:00 UTC2016-01-04 00:00:00 UTC000
Jan 42016-01-04 00:00:00 UTC2016-01-11 00:00:00 UTC000
Jan 112016-01-11 00:00:00 UTC2016-01-18 00:00:00 UTC000
Jan 182016-01-18 00:00:00 UTC2016-01-25 00:00:00 UTC000
Jan 252016-01-25 00:00:00 UTC2016-02-01 00:00:00 UTC000
Feb 12016-02-01 00:00:00 UTC2016-02-08 00:00:00 UTC000
Feb 82016-02-08 00:00:00 UTC2016-02-15 00:00:00 UTC000
Feb 152016-02-15 00:00:00 UTC2016-02-22 00:00:00 UTC000
Feb 222016-02-22 00:00:00 UTC2016-02-29 00:00:00 UTC000
Feb 292016-02-29 00:00:00 UTC2016-03-07 00:00:00 UTC000
Mar 72016-03-07 00:00:00 UTC2016-03-14 00:00:00 UTC000
Mar 142016-03-14 00:00:00 UTC2016-03-21 00:00:00 UTC000
Mar 212016-03-21 00:00:00 UTC2016-03-28 00:00:00 UTC000
Mar 282016-03-28 00:00:00 UTC2016-04-04 00:00:00 UTC000
Apr 42016-04-04 00:00:00 UTC2016-04-11 00:00:00 UTC000
Apr 112016-04-11 00:00:00 UTC2016-04-18 00:00:00 UTC000
Apr 182016-04-18 00:00:00 UTC2016-04-25 00:00:00 UTC000
Apr 252016-04-25 00:00:00 UTC2016-05-02 00:00:00 UTC101

What Hacker News says

3 sources
At least in programming languages, systems, and formal verification project code is both available and often evaluated along side the publication. For example FSCQ(https://github.com/mit-pdos/fscq-impl) from MIT, Verdi (https://github.com/uwplse/verdi) from UW, Dune(http://dune.scs.stanford.edu/) from Stanford, and many more. These are just the areas I work in, its very hard to making sweeping statement about CS as a full field since it is very diverse sub-community to sub-community.
In “Extremely angry with the state of academic CS research right now”
There is a gap between the formal specification and reality though. We published some work (coincidentally presented right after this paper at SOSP 2015) on building a real-world mathematical model of POSIX and using it to test existing filesystems; http://sibylfs.io Running SibylFS on Fscq showed up some limitations: - https://github.com/mit-pdos/fscq-impl/issues (mostly basic missing POSIXisms) - https://github.com/mit-pdos/fscq-impl/issues/2 an interesting one where the proof about truncate was incorrect in the specification and lead to very weird observable filesystem behaviour. Copy of the SibylFS paper here for the interested; http://anil.recoil.org/papers/2015-sosp-sibylfs.pdf Having said that, these are edges to be polished -- Fscq is an absolutely fantastic advancement in filesystems, and it shouldn't be too many years before we
Read the rest
can have a formally verified and specified filesystem in production.
In FSCQ: A formally verified crash-proof filesystem [pdf]

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.