Stringers
Avril-Exoplanet/Avril · Avril-Exoplanet

Two weeks, 366 stars, 0 forks: an open-source project that says "anyone can find planets," and nobody can say where the stars came from

What it is: an open-source Mac app with a Python engine. A model first picks out stars that may have more planets than the catalog lists, then automatically searches NASA's public TESS data for transit signals. It claims anyone can find planet candidates on their own computer.

Why it took off: nobody can say. Stars are steadily rising by dozens a day, yet no one on HN, Reddit, X, Chinese communities, or the media has mentioned it. 0 forks is highly abnormal for astronomy software, so the inference is private-channel reposting or star inflation. The topic hits October's hot trend of "amateurs using Claude Code to find planet candidates."

CHow you could follow it Don't copy its polished README; copy Pavel. Turn the process of "making the agent keep proving this isn't a planet" into a Skill or template, or carry it into another science field with public data. Get a real result first, then bring it to r/ClaudeAI, HN, and recommendation accounts.

Grade C: its stars have no reproducible source, so packaging it the same way will very likely not yield the same numbers. The topic is genuinely hot, but attention goes to whoever makes the discovery; the barrier is doing the research, not writing a README. Few people know about it yet
Data (updated daily) · Repo created 2026-11-05 · 398 stars · 7 days +302
GitHub · stars
020040011-1211-1411-1611-1811-20398
Data 2026-11-12 → 2026-11-20 (9 days, 9 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

Avril is an open-source workstation on the Mac that uses AI to find exoplanet candidates. It was created in November 5 and reached 366 stars in two weeks, steadily gaining dozens a day. Oddly, not one person has forked it, not one has opened an issue, and I can't find a single post discussing it online. The timing it caught is real, though: a month earlier, an amateur used Claude Code to find a planet candidate in NASA's public data, and it hit HN and Gizmodo. Below I cover what it is, why the star sources don't add up, and what someone wanting stars in this topic should copy and what to avoid.

A month ago, someone actually found a planet using Claude Code

On 2026 Oct 6, a product manager named Pavel Rabtsevich posted on r/ClaudeAI. Astronomy is his hobby. While using Claude Code to go through NASA's public TESS telescope data, he spotted something odd about a star about 116 light-years away, TIC 4206066: every 3.18 days it dimmed by roughly 0.05% for about two hours. The signal showed up across 2018, 2020, and 2025 worth of observations. He spent about two weeks running 74 analyses and writing over a thousand scripts, with Codex and a separate read-only session checking each other's work. His takeaway fits in one line: "

"Don't ask the agent whether this is a planet. Keep giving it ways to prove it isn't."

The post hit Hacker News with 302 points and 132 comments, and Gizmodo followed up with coverage 10-09. In November 6, the TESS team formally listed the star as TOI 7930. Both signals he reported became planet candidates, with periods only 0.29 seconds and 1.6 seconds off from what he had published a month earlier. Sites like agentcookbook ran another round of coverage 11-10.

The story "AI lets ordinary people do real science" was genuinely hot from October through November. Avril was created the day before TOI 7930 was announced.

What it is

On GitHub it's Avril-Exoplanet/Avril, under an Apache-2.0 license. The first line of the README reads "Exoplanet discovery for everyone." The Chinese version reads "We hope every soul that gazes at the stars will never be forgotten by time," and ends with "Among billions of stars, there may be a world waiting for you to discover it."

Features come in two parts:

  • First, pick the stars: train a model on the older Kepler star catalog, looking at parameters like temperature, mass, and radius, to estimate how many planets a star "should" have, then compare that to what the catalog has recorded. Systems that look like multi-planet systems but have only one or no planets listed get moved to the front of the queue. The repo ships with a queue of 1,000 TESS targets.
  • Then search for transits: jointly analyze light curves across multiple observing years, run BLS / TLS searches, red-noise and harmonic tests, and false-positive rejection. Each candidate's period, events, and reasons for rejection are archived, with the main pitch being "a complete evidence chain, reproducible."

The front end is a native Mac app written in SwiftUI, and the engine is Python, with CPU and CUDA support. It's not an empty shell: 317 files, 95 Python files, 34 Swift files, plus a full set of docs (science conventions, validation reports, model cards, citation format) and 5 architecture diagrams. But there's no release and no packaged .app. To use it, you have to build from source yourself, with the Xcode command line tools and a Python environment. The README itself labels it "research preview", and it hasn't reported any new discoveries.

The author's GitHub profile lists Nanjing University, with 4 followers. Their previous 11 repos topped out at 4 stars. The org account Avril-Exoplanet was registered the same day the repo was created, and it's the only repo under it. The code was pushed in one go across 11-04 and 11-05 commits, and nothing has been pushed since.

How the stars came in, day by day

DatestarGained that dayfork
11-1279—0
11-1396+170
11-14145+490
11-15188+430
11-16216+280
11-17247+310
11-18298+510
11-19356+580

(Daily GitHub star counts. The GitHub page shows 11-18 stars, 366 forks, 0 watchers, and 0 issues. 0)

The curve is a smooth upward slope, +17 to +58 per day, with no spikes from someone sharing it. Open source projects that get boosted by a recommendation feed or Hacker News usually spike to dozens or hundreds of stars in a single day, then fall off fast.

The star sources don't add up

I checked every place that could plausibly bring stars:

ChannelWhat I found
Hacker NewsNo Avril. The most recent exoplanet item is Pavel's post.
XSearched the project name and org name over the last 30 days: 0 results
RedditNo results. Searching "Avril exoplanet" only turns up Andy Weir's audiobook "Exoplanet" (11-05 release), which landed the same day the database was built. Pure coincidence.
Zhihu, V2EX, linux.do, Xiaohongshu, various weekly newslettersNone
Media and aggregator sitesNone
GitHub TrendingToo new to make any charts

The most glaring signal is the 0 forks. Astronomy software users are people who download and run it and tweak the parameters. In older repos in this field, the fork-to-star ratio runs about 20% to 40%. lightkurve (the standard library for TESS/Kepler analysis) has 550 stars and 208 forks. Google's exoplanet-ml has 324 stars and 121 forks. Avril passed exoplanet-ml's star count in two weeks, with 0 forks.

To be fair, 0 forks alone isn't unusual. On GitHub, most repos that reach 300 to 500 stars within 30 days have no more than 1 forks, and many people star things just to bookmark them. But in a field where few people bookmark and anyone who actually uses the tool will run it, this stands out.

The remaining explanations are: (1) private-circle reposts that search can't see, like classmate groups, QQ groups, and WeChat groups; or (2) star-farming, where accounts star each other's repos. This check can't show the account-level star breakdown, so there's no firm conclusion yet. One side clue: author 11-14's new repo, Neural-State-OS ("internal state modulation and observability for local LLMs"), uses the same template: a high-concept pitch, a research preview badge, and a big pile of scientific docs. By 11-18 it had 151 stars and 0 forks, and its growth curve was just as flat.

Who else is in the space

ProjectScaleCompared with Avril
lightkurve550 stars / 208 forks, since 2018Low-level Python library; you write your own code. Avril packages star selection, search, and false-positive ranking into a GUI.
NASA ExoMiner / ExoMiner++127 stars / 33 forksFocused on candidate vetting. NASA says it helped validate about 370 planets. Avril has no discoveries.
google-research/exoplanet-ml324 stars / 121 forks, since 2018Pioneering project that classifies light curves with neural networks
Planet Hunters TESS(Zooniverse)A large crowd of citizen science volunteersHumans eyeball light curves on a web page. Avril searches automatically and locally.
Claude Code / Codex analyzing directlyPavel alone, produced TOI 7930A general-purpose agent plus self-designed validation rules produced real discoveries
SpaceDataRig/space-data-rig151 stars / 8 forks, created 10-10Same "AI science crew" narrative, now stalled

(GitHub, 11-18.)

The last two lines make one point. This narrative is crowding in, and the one that actually got attention was the person using a general agent, setting their own rules, and really finding something. Not the person building a dedicated star-finding app. The more capable Claude Code gets, the less a dedicated exoplanet-search app is worth.

Real work, but nobody sees it

Avril has a clear product pitch: it uses "this star should have more planets than the catalog lists" to decide what to compute first, emphasizes an tamper-evident evidence chain, has a native Mac interface, and is bilingual in Chinese and English. Among open source astronomy tools, a consumer-grade interface and scientific docs this complete are rare.

But none of that is why it got stars, because nobody has talked about any of these features anywhere. There's no installer, so ordinary astronomy enthusiasts can't get it running. There's no story of "I used Avril to find candidate X." And 0 issues suggests few people have actually run it. Stars have come completely apart from usage.

If it were you

Bottom line: there's something to learn here, but don't follow its path. Its stars have no traceable source. A polished README on an astronomy project will most likely not get you these 366 stars. The approach that actually works in this niche is Pavel's: use AI to find something real, then talk about it in public.

Who it's for: developers who know some astronomy or another science with public data (astronomy, meteorology, seismology, bioinformatics) and are willing to spend weeks getting a real result. Graduate students and research enthusiasts who want an open source project with a story worth putting on a CV.

Who it's not for: people who only want stars and don't plan to do real research. Readers in this field run the code and check the conclusions, and an empty package won't hold up. Also not for anyone planning another "exoplanet-finding GUI". lightkurve, ExoMiner, and Zooniverse already exist, and Claude Code itself is eating into this space.

How to do it: three ways to follow, ranked from best to weakest:

  1. Build a productized version of Pavel's work: his method is to have an agent keep trying to prove the signal is not a planet. Hold out a year of data, predict on the other two years, then check the answers. Packaging that validation workflow as a Claude Code / Codex Skill or template, with his public code and process as a reference, is a much lower bar than building a full app.
  2. Change the field: take the same "AI + public science data + amateur enthusiasts" story and apply it to variable stars, asteroids, meteors, bird song, or seismic waveforms. These fields also have public data and citizen science communities.
  3. Fill the gaps Avril left: a signed .app, a "drag it in and run it" demo video, and one real candidate case worked through end to end. These three things will bring in real users more than 5 architecture diagrams.

How to get users: get a result first, then post. Pavel's path went from a post on r/ClaudeAI to Hacker News to outlets like Gizmodo. His posts had predictions, validation rules that could prove him wrong, and data and code. On the Chinese side, you could submit to GitHub recommendation feeds and astronomy enthusiast communities at the same time. Until you have a result, a beautiful README just waits for passersby.

When the window is: new observations for TOI 7930 are expected to be public around January, and the story will likely heat up again then. Ideally, get the tool and a first case out before January 2027.

What would mean I got it wrong: (1) Avril gets real forks, issues, and use cases over the next month or two. That would mean it has real users and its stars are cleaner than I estimated, and its packaging is worth studying closely. (2) Several "AI finds exoplanets" open source projects get hundreds of stars on the strength of polished READMEs alone. That would mean the topic itself draws stars and the bar is lower than I estimated. (3) The opposite: TOI 7930 follow-up data fails to confirm, or media starts reporting "AI exoplanet" false positives. The story would cool off, and any follow-up should be more cautious.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
lightkurveOpen source2018-01550 stars / 208 forks. The standard library for TESS/Kepler analysis.The low-level Python library requires you to write your own code. Avril packages star selection, search, and false-positive ranking into a Mac GUI.
NASA ExoMiner / ExoMiner++Open source2024-07127 stars / 33 forks. NASA says it helped validate about 370 planets.ExoMiner focuses on candidate vetting and has real results. Avril is a personal end-to-end tool with no published discoveries.
google-research/exoplanet-ml (AstroNet)Open source2018-12324 stars / 121 forksCNN light curve classification. Avril adds stellar-prior ranking and a native app.
RAVEN pipelineOther2026-03 (reported)Validated 118 new planets, 2,000+ candidatesProfessional teams run it on clusters. Avril is built for personal Macs.
hippke/tls, wotanOpen source2018-201966 / 180 starsA single algorithm library. Avril is a higher-level wrapper that calls BLS/TLS internally.
Planet Hunters TESS / Exoplanet Explorers(Zooniverse)WebFrom ¥2018A large crowd of citizen science volunteersHumans eyeball light curves on a web page. Avril searches automatically and locally.
Claude Code / Codex analyzing directly (Pavel Rabtsevich, TOI 7930)Big-company features2026-10HN 302 points, coverage by Gizmodo and others, produced 1 TOI candidatesA general-purpose agent plus self-designed validation rules produced real discoveries, weakening the case for dedicated star-finding software
SpaceDataRig/space-data-rigOpen source2026-10-10151 stars / 8 forks, stalledSame narrative (AI science crew + Solana attestation). Avril adds a native GUI and stellar priors.
Where users come from
  • Inference Star-farming or private-circle mutual support (QQ/WeChat groups, classmates): 366 stars, 0 forks, 0 watchers, 0 issues. The fork-to-star ratio of established astronomy repos is 20–40%. Stars rise steadily day by day with no spikes. The same author's Neural-State-OS is copying this pattern, and no public channel mentions either repo. The stargazers endpoint has been locked down by the platform, so we cannot check who starred it.
  • Inference Timing: the AI hobbyist planet-hunting wave: 10-08 Reddit/HN post "I used Claude Code to find a planet" (302 points on HN), Gizmodo 10-09. After TOI 11-06 was announced, agentcookbook and others ran another round 7930 11-10. Avril built its repo 11-05, and its tagline fits the moment, but we found no evidence of referral traffic.
  • Inference HN / Reddit / X / Chinese communities / media / trending: Our HN database, x-radar, Jina, Exa and Brave each return 0 results. A repo under 60 days old cannot get onto trending.

Avril-Exoplanet/Avril: an "AI planet hunting" workstation that can't find an audience yet keeps gaining stars.

Bottom line: Avril's stars can't be explained by any visible traction. It hit about 360 stars in two weeks, yet forks, watchers, issues and PRs are all 0. Searches of HN, Reddit, X, Chinese communities, media and aggregator sites turn up not a single third-party mention, and the only push was on the day the repo was created. The star curve is a smooth straight line at +17~58 per day, not the spike a real wave of attention produces. The most likely explanations are circulation within a private circle or friend network, or outright star-buying and mutual starring. The same author's Neural-State-OS, opened 11-14, follows the same playbook (a grand concept, a research-preview badge, a pile of 'scientific' docs, 0 forks), and gained +107 stars in two days. The timing was real, though: in October a story went viral about a hobbyist using Claude Code to find planet candidates in TESS data. But Avril did not pick up any verifiable traffic from that story.

1. What it is

  • Repo: github.com/Avril-Exoplanet/Avril, Apache-2.0,2026-11-05 licensed. The organization account Avril-Exoplanet was also registered the same day, has 11-05 followers, and owns only this repo (checked via the GitHub API, 0 11-18).
  • What it is: a native macOS SwiftUI workstation with a Python engine (CPU/CUDA). It has two parts. (1) "Planetary Census Gap AI": trained on a frozen Kepler DR25 catalog, it ranks 1,000 TESS targets by how much they look like multi-planet systems that the catalog is missing planets for (the README reports a top-decile lift of 4.4–4.8×). (2) Transit search: BLS/TLS, cross-sector voting, red-noise and harmonic tests, and pixel localization, with an emphasis on a complete, reproducible evidence chain.
  • The codebase is not an empty shell: 317 files, 95 .py files (about 1.7 MB) and 34 .swift files. But PNG/JPG images take up about 26 MB, and the README is bilingual (Chinese and English), with lyrical lines like "we hope that every soul gazing at the stars will never be forgotten by time" and 5 large architecture and validation images. There is no release and no signed .app, so you have to build from source.
  • Author: committer ShutongLiang (display name Lns, company field reads Nanjing University, email is a QQ Mail address), 4 followers; the repo's previous 11 maximum was 4 stars (GitHub API). Three commits: 11-04 20:42 "Open-source Avril…" (one squash commit pushing all the code), 11-05 08:15 rebrand, 11-05 15:03 point the links at the new org. No pushes since.

2. Growth data

DatestarDaily +fork
11-1279—0
11-1396170
11-14145490
11-15188430
11-16216280
11-17247310
11-18298510
11-19356580

Source: our GitHub repo_day database. 11-12 was the first time we captured it. It probably crossed our star threshold for inclusion around 11-10 20. At the GitHub API check 11-18 it had 366 stars, 0 forks, and subscribers_count 0.

  • Our repo database flagged it as suspect for "almost zero forks" (≥300 stars, forks ≤1).
  • For comparison, across the whole exoplanet/TESS topic Avril reached the 4th spot by stars in two weeks. That is ahead of google-research/exoplanet-ml (324 stars / 121 forks, created 2018 years ago) and close to lightkurve (550 stars / 208 forks, 8 years old). The fork-to-star ratios of the established repos in this field sit at 20%–40%, while Avril's is 0%. Real users of astronomy software clone and fork to run and modify it, so 366 stars with 0 forks is highly abnormal for this field.
  • That said, among new repos that gained 300–500 stars within 30 days of creation, 55.5% (399/719) had forks ≤1 (our GitHub repo database). Zero forks is common among new repos, so that alone is not proof of wrongdoing. It stands out because astronomy is a field of heavy use with very few "bookmark-only" users.
  • We can't pull the stargazer breakdown: GitHub's stargazers endpoint returned 404/403 for our token, and GraphQL returned totalCount 0 (even for 0kzh/glisse, so it looks like the platform has tightened access), so we can't check when the starring accounts were registered or how active they are.

3. Where users came from (places we searched)

ChannelResult
Hacker NewsOur Hacker News database does not include Avril. The most recent exoplanet-related item is 10-08's "I think I found a planet nobody knew existed. I used Claude Code to find it" (302 points / 132 comments).
Xx-radar searched "Avril exoplanet", "Avril-Exoplanet" and "Neural-State-OS" over the last 30 days and found 0 results.
RedditBrave and Exa return no posts about Avril. Searching "Avril exoplanet" only surfaces Andy Weir's audiobook "Exoplanet" (11-05 released, same day as the repo was created, pure coincidence).
Chinese communities (Zhihu / V2EX / linux.do / Xiaohongshu / Ruan Yifeng's weekly)Jina and Brave found nothing.
Media and aggregators.None. The AI news aggregator MindPattern indexed the author's other repo, Neural-State-OS (11-16, tagged "low signal"), but did not pick up Avril.
trendingThe repo is less than 60 days old, so it can't make the charts (see the rule in SCHEMA.md). It did not get there through trending.
Ads / Product Hunt.It's an open-source repo, so none.

Conclusion: no public channel we checked accounts for these 360 stars. The remaining explanations are: (1) private-circle forwarding, such as classmates at Nanjing University or QQ/WeChat groups (not searchable, but these usually produce a few forks and issues); (2) star-farming or mutual starring; or (3) a small push through GitHub's own recommendation feed (Explore / For you). The curve is steady growth over many days with no spikes, and the same author used the same pattern on two repos at once. Both of those point toward (1) or (2), not a genuine wave of attention.

4. Timing: a real "AI + amateur planet hunting" wave

  • 2026-10-06–10: Pavel Rabtsevich posted on r/ClaudeAI that he had used Claude Code to find a transit signal for TIC 4206066 in TESS data. It reached 302 points on HN, and Gizmodo (10-09) and Les Numériques (10-08) covered it. 11-06 the TESS team listed the star as TOI 7930, and both signals became planet candidates. agentcookbook (11-10), readmex and kblip then covered it again (sources: agentcookbook.dev/r/claude-code-codex-planet-hunt, gizmodo.com/did-claude-help-an-amateur-astronomer-discover-a-new-planet-2000824393, news.ycombinator.com/item?id=50002665).
  • Avril was created 11-05, right in the middle of this wave, and its tagline ("anyone can find planet candidates on their own computer") matches it exactly. But there is no evidence it picked up any traffic from the wave: it is not in the comment sections of those posts, and no aggregator picked it up along the way.
  • Similar projects from the same period: SpaceDataRig/space-data-rig (created 10-10, a "five-seat AI science crew" for transit detection with Solana attestation, 151 stars / 8 forks, now stalled), zczc/variable-star-discovery (created 11-10, 0 stars), and victorfcp4/Space-Lab (a web page for citizen science on home computers). These show that "AI lets anyone make astronomical discoveries" is a narrative that many projects are rushing into.

5. Competitors

NameWhereLaunchedScaleHow Avril is different
lightkurveOpen source2018-01550 stars / 208 forks, the de facto standard library for TESS/Kepler analysis.lightkurve is a low-level library that requires writing your own code. Avril packages target ranking, search and false-positive vetting into a native Mac GUI.
NASA ExoMiner / ExoMiner++Open source / major institutions (NASA).2024-07127 stars / 33 forks. NASA says it has helped validate about 370 planets.ExoMiner does deep-learning false-positive vetting. Avril is a full pipeline for individuals, from star selection to search, with no peer-reviewed discoveries.
RAVEN pipelineAcademic2026-03 coverage.Validated 118 new planets and 2,000+ candidates.Professional teams run it on clusters. Avril is built for personal computers.
google-research/exoplanet-ml(AstroNet)Open source / big companies2018-12324 stars / 121 forksThe pioneering CNN light-curve classifier. Avril adds stellar-prior ranking and a GUI.
hippke/tls, wotanOpen source2018–1966 / 180 starsAvril calls BLS, with optional TLS. It is a higher-level wrapper.
Planet Hunters TESS / Exoplanet Explorers(Zooniverse)WebFrom ¥2018Hundreds of thousands of citizen-science volunteers.That project relies on people visually inspecting light curves on the web. Avril runs automated search locally.
Direct analysis with Claude Code / Codex (Pavel's approach).Big-company features2026-10 went viral.A single TOI candidate, 302 points on HN.General-purpose agents with your own detection rules are more flexible, and this path is eroding the value of purpose-built planet-hunting software.
SpaceDataRig/space-data-rigOpen source2026-10-10151 stars / 8 forksThe same narrative (an AI science crew), but Avril adds a native app and stellar priors.

6. Differentiation

  • On product, it does have a clear pitch: using a "planetary census gap" prior to decide which stars to compute first, stressing a tamper-evident evidence chain, a native Mac GUI (no WebView), identical CPU/CUDA results, and bilingual docs. Among open-source astronomy tools, few offer a consumer-grade GUI this complete alongside scientific documentation packaging (SCIENTIFIC_CONTRACT, VALIDATION, model cards, CITATION.cff).
  • But these differences are not why it got its stars. Nobody discusses these features anywhere. There is no release, so a typical amateur has to install Xcode CLT and a Python environment before it runs. There is no case of "I used Avril to find candidate X." Stars are completely decoupled from usage (0 forks, 0 issues).

7. Takeaways

  • On the positive side, it launched just as Pavel's story ignited the "AI lets amateurs do real science" narrative, and its tagline speaks directly to romantic sentiment ("Among billions of stars, there may be a world waiting for you to discover it"). The template does get used by others. The same author quickly moved to Neural-State-OS, which "gives models a sense of feeling" and copies the README structure, the research-preview badge and the whole documentation set.
  • If you really want to do this, what you are missing is a discovery story like Pavel's: run your tool and find a real TOI candidate, then tell it on r/ClaudeAI, r/space or HN. A signed .app and a demo video that runs with a drag-and-drop bring in real users far better than 5 architecture diagrams.
  • Warning: for this kind of "grand concept + polished README + 0 forks" repo, stars should not be treated as a demand signal.

8. Uncertain

  • Who the starring accounts are: the platform has tightened access to the stargazers endpoint, so we cannot check. Star-farming versus private-circle forwarding cannot be confirmed.
  • Whether it spread through QQ/WeChat groups, Nanjing University courses or clubs: private channels we cannot search, so we cannot rule them out.
  • Whether the code actually runs and whether the science holds up: we did not run it. The README itself calls it a "research preview," and no new discoveries have been reported.

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.