HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
GrapheneOS
os-issue-tracker
Security & Privacy2021–2026
GrapheneOS / os-issue-tracker

os-issue-tracker

Issue tracker for GrapheneOS Android Open Source Project hardening work. Standalone projects like Auditor, AttestationServer and hardened_malloc have their own dedicated trackers.

32Distinct people
45Mentions
2Explicit recommenders
658GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Issue tracker for GrapheneOS Android Open Source Project hardening work. Standalone projects like Auditor, AttestationServer and hardened_malloc have their own dedicated trackers.

GitHub

Where it is used

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

What people are saying

Rooting is a very bad idea. https://madaidans-insecurities.github.io/android.html#rootin... But GrapheneOS is fully open source and provides great build instructions, so you…

Andromxda used a recommendation phrase. 2 indexed comments match. 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

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:04:58 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 year45 dated mentions

Observed mentions: 2021-02-15 20:32:42 UTC to 2026-09-12 10:24:47 UTC.

051015202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 18 mentions; 0 submissions, 18 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
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC909
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC404
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC808
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC18018

What Hacker News says

4 sources
I've been using it for the past year and it works well. With one exception. The couple of times I've called emergency services, they were not able to detect my location since GrapheneOS does not support the protocol for this. So, I had to waste time giving directions. It's a tradeoff for privacy vs safety. It might be something to think about before, say, putting this on someone's phone who has a medical condition or is elderly. https://github.com/GrapheneOS/os-issue-tracker/issues/1174
In DivestOS ROM shuts after ten years
I have to agree with mid-kid here. GrapheneOS is great for security, but some of that ends up directly in conflict with privacy. For example years ago I opened an issue around runtime-patching applications (https://github.com/GrapheneOS/os-issue-tracker/issues/284) and was told it didn't make sense in the OS. Putting aside the validity of arguments on either side of that issue, runtime patching allows me to very quickly excise large swaths of anti-privacy code across every app on my phone. If I was to switch to GrapheneOS I'd have to accept that I'd be giving up a fair amount of privacy for the added security.
In How de-Googled is Lineage OS?
I used CyanogenMod/LineageOS for the better part of a decade and switched to GrapheneOS a couple years ago and haven't looked back. When it comes to security (and privacy), GrapheneOS blows LineageOS out of the water in pretty much every way, e.g.: - Arbitrary-length encryption passphrases - General security hardening: Memory hardening, sandbox hardening etc. - Non-rooted (i.e. much higher security barriers for malicious apps to take over control over your phone) - No userdebug mode (LineageOS ROMs are often development builds which weaken the security of the OS, see e.g. https://github.com/GrapheneOS/os-issue-tracker/issues/284#issuecomment-690417436 ) - Fully secured boot chain (in other words: A thief won't be able to do much with your phone) - Sandboxing of Google services (*if* you want to use them), i.e. Google no longe
Read the rest
r has admin access to your phone - Being able to restrict internet access for certain apps (that's a huge one in my book) - Being able to grant apps access only to select contacts from your contact list (contact scopes), and only select files/folders (storage scopes) See https://grapheneos.org/features for a much longer list. Now that I'm thinking about it, some of the above features have become so natural to me, that I find it wild that other AOSP-based ROMs (including Google's) don't have them. Moving away from GrapheneOS would be incredibly painful for me.
In How de-Googled is Lineage OS?
Are you suggesting GrapheneOS is bug-free? ... https://github.com/GrapheneOS/os-issue-tracker/issues It was referring to the overall experience to which I was referring, not the OS specifically ("it's a buggy ride", it = the ride, not GrapheneOS) I imagine a lot of the issues are because of the apps not testing on GrapheneOS. But I've had lots of little issues: - Nova Launcher on a daily basis stopped working when pressing the right button (the 'overview' button). I had to kill the stock Launcher app to fix it, interestingly. Had to revert to the stock launcher - 1Password frequently doesn't trigger auto-fill in Vivaldi - Occasionally on boot the SIM unlock doesn't trigger - Camera crashing often (yes, "could be hardware"...I read the forums/GitHub issues) More that I can't remember. It's a bit frustrating. But don't get me wrong, I appre
Read the rest
ciate the project. I'm not going to go back to stock
In Google's Gemini AI caught scanning Google Drive PDF files without permission

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.