HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
static-analysis-engineering
CodeHawk-C
Python2022–2022
static-analysis-engineering / CodeHawk-C

CodeHawk-C

CodeHawk C Analyzer: sound static analysis of memory safety (undefined behavior)

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

What to know before exploring

What it is

CodeHawk C Analyzer: sound static analysis of memory safety (undefined behavior)

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

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

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 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 hour2 dated mentions

Observed mentions: 2022-12-21 22:22:18 UTC to 2022-12-21 23:40:39 UTC.

012022-12-21 22:00:00 UTC to 2022-12-21 23:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 21, 22:002022-12-21 23:00:00 UTC to 2022-12-22 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 21, 23: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
Dec 21, 22:002022-12-21 22:00:00 UTC2022-12-21 23:00:00 UTC101
Dec 21, 23:002022-12-21 23:00:00 UTC2022-12-22 00:00:00 UTC101

What Hacker News says

1 sources
In theory, sound static analyzers could be another method by which this is achieved in existing projects. They claim to be able to catch all instances of this. Some examples of sound static analyzers include: https://www.absint.com/astree/index.htm https://github.com/NASA-SW-VnV/ikos https://github.com/static-analysis-engineering/CodeHawk-C I have planned to try using them on OpenZFS for a while, but I am still busy reviewing and fixing reports made by conventional static analyzers. I plan to look into these next. That said, at least one of them claims to be able to prove the absence of issues in C that checked C’s documentation explicitly says it cannot prevent. The obvious one is use-after-free.
In Checked C

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.