nyxt

atlas-engineer/nyxt

Nyxt - the hacker's browser.

Ship status

Gone silent

No push in over 120 days. A quiet repo may also be a finished one.

Last push
Feb 26, 2026
218 days ago
Ship score
10/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 11,001 → 11,024 (Aug 18 – Sep 29, 2026)
+10 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
11K
Forks
467
Open issues
147
Watchers
126
Primary language
Common Lisp
License
Unknown
Created
Apr 8, 2017
Owner
atlas-engineer · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 1 startup in the directory ships primarily in Common Lisp.

Topics

#browser#common-lisp#emacs#extensible#hacker#keyboard-driven#lisp#power-user#productivity#vim#web-browser

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose something else instead, and put os_startup at 42% (self-hostable 33%, hosted offering 11%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: silent — last push 2026-02-26This is the badge for atlas-engineer/nyxt, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/atlas-engineer/nyxt.svg)](https://ossean.com/atlas-engineer/nyxt)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.