HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
rocq-prover
rocq
OCaml2014–2026
rocq-prover / rocq

rocq

The Rocq Prover is an interactive theorem prover, or proof assistant. It provides a formal language to write mathematical definitions, executable algorithms and theorems together with an environment for semi-interactive development of machine-checked proofs.

34Distinct people
44Mentions
1Explicit recommenders
5.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Rocq Prover is an interactive theorem prover, or proof assistant. It provides a formal language to write mathematical definitions, executable algorithms and theorems together with an environment for semi-interactive development of machine-checked proofs.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I recently learned about some limitations in both Coq and Lean theorem prover after watching the video by Kevin Buzzard on formalization of math in Lean. He did some claims…

xvilka used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM 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 year44 dated mentions

Observed mentions: 2014-09-07 23:44:29 UTC to 2026-09-05 14:42:29 UTC.

0510152014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC826
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC514
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC13112
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC606
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
The Rocq Prover The Rocq Prover is an interactive theorem prover, or proof assistant. It provides a formal language to write mathematical definitions, executable algorithms and theorems together with an environment for semi-interactive development of machine-checked proofs. Installation Please see https://rocq-prover.org/install. Information on how to build and install from sources can be found in INSTALL.md. Documentation The sources of the documentation can be found in directory doc. See doc/README.md to learn more about the documentation, in particular how to build it. The documentation of the last released version is available on the Rocq web site at rocq-prover.org/docs. See also the Rocq wiki, and the Rocq FAQ, for additional user-contributed documentation. The documentation of the master branch is continuously deployed. See: Reference Manual (master) Documentation of the standard library (master) Documentation of the ML API (master) Changes The Recent changes chapter of the reference manual explains the differences and the incompatibilities of each new version of the Rocq Prover. If you upgrade Rocq, please read it carefully as it contains important advice on how to approach some problems you may encounter. Questions and discussion We have a number of channels to reach the user community and the development team: Our Zulip chat, for casual and high traffic discussions. Our Discourse forum, for more structured and easily browsable discussions and Q&A. See also rocq-prover.org/community, which lists several other active platforms. Bug reports Please report any bug / feature request in our issue tracker. To be effective, bug reports should mention the OCaml version used to compile and run Rocq, the Rocq version (coqtop -v or rocq -v), the configuration used, and include a complete source example leading to the bug. Contributing to Rocq Guidelines for contributing to Rocq in various ways are listed in the contributor's guide. Information about release plans is at https://github.com/rocq-prover/rocq/wiki/Release-Plan Supporting Rocq Help the Rocq community grow and prosper by becoming a sponsor! The Rocq Consortium can establish sponsorship contracts or receive donations. If you want to take an active role in shaping Rocq's future, you can also become a Consortium member. If you are interested, please get in touch!
Read the full README on GitHub

What Hacker News says

13 sources
The kernel of a proof assistant is one of the most important components because it represents the foundation of reasoning in that logical system. There's a lot of introductory literature now, such as [0][1][2][3]. > What kind of axiomatic basis is being used in ACL2 and similar systems? ACL2 uses first-order logic and term rewriting, but this significantly hinders proof automation (done by ad-hoc searches). > Or do the different systems have significant differences with how and what they can prove? Yes. First-order logic can only quantify over individual elements of a set, second-order logic can quantify over sets, and so on. Higher-order logic is the foundation of assistants like Isabele/HOL light, which let you use classical reasoning. Alternatively (and better from an engineering standpoint) are assistants based on type theory, such as
Read the rest
Agda, Coq and Lean. Their kernels are just type checkers, which are relatively small programs, so theorem proving in those systems is literally just functional programming with a fancy type system (though exactly how those proofs are constructed is a UX choice). > Do the systems allow explorations in reverse maths, trying to derive stuff with as little axioms as possible? Yes, in Coq you can print out the axioms (on top of the type system) that a result depends on. See [4] for information on Coq's logic and what axioms you can safely add (they are necessary for certain areas of math). [0] (Coq) https://softwarefoundations.cis.upenn.edu/ [1] (Agda) https://plfa.github.io/ [2] (Isabelle) http://concrete-semantics.org/ [3] (Lean) https://www.ma.imperial.ac.uk/~buzzard/xena/natural_number_g... [4] https://github.com/coq/coq/wiki/The-Logic-of-Coq
In The Fundamental Theorem of Algebra in ACL2
> Imagine for a second that your favourite programming language or the one you use at work was called "Penis" No need to imagine, "bit" is pronounced in French exactly like "bite", which means basically the same thing as "cock". > How fun would it be when you told someone "we use Penis where I work to implement our AwesomeSoftware™? You get used to it. Talking about "cock twiddling" sounds strange at first, and is annoying. But since we're French we can't really hope that this will change anytime soon. Anyways, I'm all for changing the name, but hope we can keep the French origin. "LPC" for "Le Prouveur Coq" is a good idea https://github.com/coq/coq/wiki/Alternative-names.
In Coq mulls new name for programming language
From their wiki page (https://github.com/coq/coq/wiki/Alternative-names): > Reason for discarding: Con is French slang for vulva. This will inevitably lead to categorical jokes about co-con aka... the problem we started with. > Reason for discarding: [...] Also consider the standard clam (coque) metaphor for female genitalia. > Reason for discarding: [...] A translation of the French word. Watch out: "rooster" is also slang for "penis". > Reason for discarding: [...] Even if one ignores that it apparently means “vagina” in Haitian Creole (as pointed out by Lélio), the fact that phonetically, it's apparently slang for “a communist” in French (as pointed out by Matthieu) should be a non-starter [...] > Reason for discarding: "peep" also has a strong sexual connotation in French. Should really be avoided. > Reason for discarding: "Gaule" can
Read the rest
be definitely used to mean "erection" in French. Thank you for your hard and dedicated work ! :)
In Coq mulls new name for programming language
Interesting, and that's reflected in the alternative names discussion [1]: > Using the "coke" pronunciation, possibly written "Côq" Because Côq is an extremely addictive tool. In French, it would be pronounced with a closed "o" reminiscent of the "o" of "coke" in English. Good for those fond of playing with words, oh geez, these lines of high quality Côq made me so happy. [1] https://github.com/coq/coq/wiki/Alternative-names
In Coq mulls new name for programming language
From https://github.com/coq/coq/wiki/Alternative-names > others getting harassed when they said they were working on Coq It's hard for me to imagine anyone getting harassed over this, who are these people who haven't moved past puberty but are in a professional environment? Is there any examples of this happening in the wild online? Looking through the examples, if the problem is that people cannot hear something that sounds like "cock" without harassing people, you probably need to chose a name that sounds nothing like it, rather than just a slight modification. Coquito, PeaCoq, Coqpit, Côq, Coq au vin, Le Coq, Coqorico, Coqueluche, Coque, Coqroach etc all sound too familiar and if the purpose is to stop harassment, none of those would be real options. Edit: on second thought, I wonder if the people who harassed others over using Coq als
Read the rest
o harass people who are using Git. Why/why not?
In Renaming Coq

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.