HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
david-a-wheeler
mmverify.py
Python2026–2026
david-a-wheeler / mmverify.py

mmverify.py

Metamath verifier in Python

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

What to know before exploring

What it is

Metamath verifier in Python

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 3-hour interval2 dated mentions

Observed mentions: 2026-07-30 13:45:08 UTC to 2026-08-02 05:13:46 UTC.

012026-07-30 12:00:00 UTC to 2026-07-30 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 30, 12:002026-07-30 15:00:00 UTC to 2026-07-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-30 18:00:00 UTC to 2026-07-30 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-30 21:00:00 UTC to 2026-07-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-31 00:00:00 UTC to 2026-07-31 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-31 03:00:00 UTC to 2026-07-31 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-31 06:00:00 UTC to 2026-07-31 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-31 09:00:00 UTC to 2026-07-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-31 12:00:00 UTC to 2026-07-31 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-31 15:00:00 UTC to 2026-07-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-31 18:00:00 UTC to 2026-07-31 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 31, 18:002026-07-31 21:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-08-01 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 03:00:00 UTC to 2026-08-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 06:00:00 UTC to 2026-08-01 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 09:00:00 UTC to 2026-08-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 12:00:00 UTC to 2026-08-01 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 15:00:00 UTC to 2026-08-01 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 18:00:00 UTC to 2026-08-01 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 21:00:00 UTC to 2026-08-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-02 00:00:00 UTC to 2026-08-02 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-02 03:00:00 UTC to 2026-08-02 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 2, 03:00

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
Jul 30, 12:002026-07-30 12:00:00 UTC2026-07-30 15:00:00 UTC101
Jul 30, 15:002026-07-30 15:00:00 UTC2026-07-30 18:00:00 UTC000
Jul 30, 18:002026-07-30 18:00:00 UTC2026-07-30 21:00:00 UTC000
Jul 30, 21:002026-07-30 21:00:00 UTC2026-07-31 00:00:00 UTC000
Jul 31, 00:002026-07-31 00:00:00 UTC2026-07-31 03:00:00 UTC000
Jul 31, 03:002026-07-31 03:00:00 UTC2026-07-31 06:00:00 UTC000
Jul 31, 06:002026-07-31 06:00:00 UTC2026-07-31 09:00:00 UTC000
Jul 31, 09:002026-07-31 09:00:00 UTC2026-07-31 12:00:00 UTC000
Jul 31, 12:002026-07-31 12:00:00 UTC2026-07-31 15:00:00 UTC000
Jul 31, 15:002026-07-31 15:00:00 UTC2026-07-31 18:00:00 UTC000
Jul 31, 18:002026-07-31 18:00:00 UTC2026-07-31 21:00:00 UTC000
Jul 31, 21:002026-07-31 21:00:00 UTC2026-08-01 00:00:00 UTC000
Aug 1, 00:002026-08-01 00:00:00 UTC2026-08-01 03:00:00 UTC000
Aug 1, 03:002026-08-01 03:00:00 UTC2026-08-01 06:00:00 UTC000
Aug 1, 06:002026-08-01 06:00:00 UTC2026-08-01 09:00:00 UTC000
Aug 1, 09:002026-08-01 09:00:00 UTC2026-08-01 12:00:00 UTC000
Aug 1, 12:002026-08-01 12:00:00 UTC2026-08-01 15:00:00 UTC000
Aug 1, 15:002026-08-01 15:00:00 UTC2026-08-01 18:00:00 UTC000
Aug 1, 18:002026-08-01 18:00:00 UTC2026-08-01 21:00:00 UTC000
Aug 1, 21:002026-08-01 21:00:00 UTC2026-08-02 00:00:00 UTC000
Aug 2, 00:002026-08-02 00:00:00 UTC2026-08-02 03:00:00 UTC000
Aug 2, 03:002026-08-02 03:00:00 UTC2026-08-02 06:00:00 UTC101

What Hacker News says

2 sources
As it happens, the Python verifier mmverify.py has an even simpler soundness bug [0], and so far I've reviewed two independent AI-written verifiers that have replicated that bug, since they apparently really like to copy the strategy from mmverify.py. A sound verifier isn't too difficult to write in terms of architecture (I just wrote one myself for differential testing [1]), but it requires some close attention to the details. That is to say, the Swiss-cheese approach definitely lends authority, but individual implementations are unfortunately not as foolproof as they're made out to be. [0] https://github.com/david-a-wheeler/mmverify.py/issues/30 [1] https://github.com/LegionMammal978/mm-verifier-tests/blob/ma...
In Postmortem for Kernel Soundness Bug #14576

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.