mrkeyoor.com_
Tue 29 Sept 06:36 UTC
Dev Toolsevaluationupdated 29 Sept 2026

fermats-last-theorem review

Fermat's Last Theorem in Lean 4 publishes a formal proof of the theorem for positive natural numbers and exponents of at least 3. It includes a six-step map of the argument and offline browser pages, but Anthropic labels it a research artifact that will not be maintained or accept contributions.

Verdict

Our 3-CPU, 8 GB sandbox did not run commit 6e837e7 because our harness has no Lean ecosystem path and the repository has no Dockerfile. Treat this as a proof artifact to browse and audit. It is neither a turnkey package nor a maintained dependency, and it fits readers who need the exact Lean statements and dependency trail.

We ran it

Screenshot of fermats-last-theorem (github.com/anthropics/fermats-last-theorem)

Answers from our run

Did you run fermats-last-theorem yourself?

No. Its code is Lean, and it carries no manifest our lab installs from, and no Dockerfile, so there was nothing standard to install, build or test. This review is written from the repository's own documentation.

Who should not use fermats-last-theorem?

Developers seeking a maintained Lean library: the README says the repository is not maintained and does not accept contributions.

What are the alternatives to fermats-last-theorem?

Imperial College London FLT, FLT Regular, Mathlib. Treat this as a proof artifact to browse and audit.

Setup1/5No Dockerfile or supported path in our Lean-free sandbox
Docs5/5Proof map, offline browser, checks, limits, and attribution
Community2/51,237 stars, but explicitly unmaintained and closed to contributions
Maturity3/5Pinned research artifact with no GitHub release

Who it’s for

Lean users who want to inspect a full formalization of the Frey, Serre, Ribet, Wiles, and Taylor-Wiles argument.
Mathematicians who prefer following theorem dependencies in a browser before opening generated Lean source.
Formal-methods researchers studying a large proof produced by AI agents and checked by Lean.
Archivists who want a pinned, Apache-2.0 research artifact rather than an evolving package.

Who it’s NOT for

Developers seeking a maintained Lean library: the README says the repository is not maintained and does not accept contributions.
Readers looking for a hand-written tutorial: comments were removed, names are machine-generated, and the README says the code was written to be checked rather than read.
Windows users who want to rebuild it locally: the README supports Linux and macOS and warns that some paths are too long for Windows.
Teams requiring a containerized verification path: our sandbox found no Dockerfile, and the repository expects Elan, network access, and host tooling.
Operators without permission to tune the host: issue 10 records builds hitting Linux's memory-map limit, with the successful workaround requiring a sysctl change.

Setup reality

We did not run commit 6e837e7 in our 3-CPU, 8 GB Debian sandbox. Our harness has no supported Lean ecosystem path, and the repository has no Dockerfile, so there was no recognized install, build, or test command to execute. No build or test result came from our box.

The documented route needs Elan, Lean 4.33.1, Mathlib v4.33.0, network access, and a source build of Mathlib. The optional comparator and nanoda checks add Linux shell tools, Python, Git, Rust tooling, and downloaded checker sources. It does not call for application credentials or a hosted service.

Linux or macOS is required, and the README rules out Windows because of long paths. Issue 10 shows another host-level catch: a reporter's build succeeded only after raising Linux's memory-map limit with sysctl. An unprivileged container may not be allowed to make that change.

The final theorem depends on three standard Lean axioms

The repository states Fermat's Last Theorem for positive natural numbers and exponents of at least 3, then connects that statement to Mathlib's formulation. Its default target also checks that the final theorem depends on exactly three standard Lean axioms. Those are strong, inspectable claims in the source. They are still the project's claims rather than results from our sandbox, because we did not complete an independent build.

Anthropic describes this as a research artifact and says it is neither maintained nor open to contributions. That sentence should control your expectations. The useful object is a pinned proof tree at commit 6e837e7. A roadmap, support channel, and release cadence do not come with it. The source was assembled by AI agents, with Lean used as the arbiter, and the README warns that generated names may disagree with the mathematical meaning of their statements.

The browser exposes 29,511 theorem pages

Opening individual generated files is the hard way to understand this repository. The bundled html/ directory is about 390 MB and contains pages for 29,511 theorems and 1,450 definition modules. Each theorem page shows its Lean statement, what it cites, what cites it, and an expandable dependency graph. The static site works offline, so a clone doubles as a browsable archive without a web server.

The pages draw a clear boundary between source and explanation. The exact Lean statement is authoritative, while English summaries and suggested references were generated automatically. Browser testing covered Chromium-based software only. That makes the site a good index and a poor substitute for reading the formal statement when a detail matters. PROOF-PATH.md is the better starting point for the mathematical route because it names the theorem carrying each step.

What happened when we ran it

Our 3-CPU, 8 GB Debian sandbox did not run commit 6e837e7. The harness found no supported ecosystem for Lean, and the repository contains no Dockerfile that could supply one. It therefore produced no install duration, dependency count, build result, test count, or vulnerability scan. There is no failure log to interpret because no build command was started.

That result says something narrow but useful: this repository falls outside an ordinary automated project runner. It does not contradict the verification account in the README, and it does not confirm it. Anyone who needs independent assurance must reproduce the Lean build and the additional checkers on a prepared host. Our unprivileged container, which had no secrets, only established that the project does not provide a container path our lab could execute.

Rechecking needs Lean 4.33.1 and control of the host

The documented path starts with Elan, Lean 4.33.1, Mathlib v4.33.0, and network access. Mathlib is compiled from source because the pinned toolchain lacks a matching prebuilt package. The repository supports Linux and macOS, while warning that some paths are too long for Windows. Comparator and nanoda are separate verification routes with more tools to install, so lake build is only the first gate.

Issue 10 records a less obvious Linux requirement. Several fresh builds reportedly failed while reading compiled .olean files even though those files existed. A maintainer traced the behavior to the host's memory-map limit, and the reporter completed the build after increasing vm.max_map_count through sysctl. The issue remains open. That workaround needs host privileges, which rules out some managed runners and locked-down containers before CPU or memory capacity even enters the discussion.

The six-step map limits the scope of the named theorems

PROOF-PATH.md moves through reduction to prime exponents, the Frey package, irreducibility, modularity, level lowering, and the vanishing of a weight-2 cusp-form space. More useful than that outline is its statement of scope. The document says which forms of results associated with Mazur, Langlands-Tunnell, Wiles, and Ribet appear in the tree, then names broader versions it does not prove. That distinction helps a specialist avoid inferring a general theorem from a purpose-built lemma.

The attribution record identifies 106 files with material from the Imperial College London FLT project or flt-regular, plus 23 files that reproduce Mathlib text. The README also says comments were removed apart from limited notices, docstrings, and citations. So the proof may be machine-checkable while remaining awkward to learn from line by line. The dependency map and attribution table carry much of the explanation that ordinary library source would provide.

A September 24 push does not make this maintained

GitHub showed 1,237 stars and 6 open issues on September 29, 2026, and the latest push was September 24. The releases endpoint returned no published release. Those dates show recent publication work and reader attention, but the repository's own status is clearer: no maintenance and no contributions. Issue replies can still resolve a build problem, as happened in issue 10, without turning the artifact into a supported project.

Choose this repository when you want the completed claim, its exact formal statements, and a browser-visible dependency trail. Choose ImperialCollegeLondon/FLT when you want to work with an active formalization, flt-regular when the regular-prime case matches your research, or Mathlib when reusable Lean mathematics is the goal. For this repository, open the proof map before considering any local integration.

Alternatives

ProjectWhat it isPick it when
Imperial College London FLTAn ongoing collaborative Lean formalization of Fermat's Last Theorem.pick this instead when you want an active project whose library is still being developed.
FLT RegularA Lean proof of Fermat's Last Theorem for regular prime exponents.pick this instead when a narrower theorem with a conventional community project is enough.
MathlibLean 4's community mathematics library and the foundation used by this proof.pick this instead when you need reusable formal mathematics rather than one frozen proof artifact.

What people are saying

  1. [hackernews] Fermat's Last Theorem in Lean 4
  2. [velocity-scout] anthropics/fermats-last-theorem

Sources

  1. Fermat's Last Theorem in Lean 4 README
  2. The route of the proof
  3. Attribution and third-party material
  4. Commit 6e837e7
  5. Issue 10: lake build memory-map limit

More dev tools reviews

omarchy-workspace-layout · yjs · ffuf · ipadecrypt · coursebook · ink · the whole board →