I recommend https://issinfo.net/artemis over the surge of vibe coded Artemis II trackers. Seen two others so far and they've all had major inaccuracies either regarding trajectory, current distance, or current mission state. One even said the remaining mission time was over 400 days. They all obviously used Claude Code.
I did not use claude code, but codex, and I am fetching space weather from NOAA SWPc, trajectory, distance, speed, and comms delay are computed from NASA's published Artemis II mission plan parameters, not pulled live from NASA telemetry. Also, the current discrepancy is likely caused by the orbital phase and reference model being used. tracker shows about 192,000 km, while NASA's AROW shows about 80,000 miles, which…
Also, it’s pretty common to see people immediately label projects as “AI slop.” There are quite a few folks who react that way right away, like @jug did here. That reaction is somewhat expected given how quickly AI has taken off and the existential/job-security concerns many computer engineers are dealing with right now, including the massive layoffs at Google 1-2 years ago.
At the end of the day, using AI to help write code is not that different from hiring a freelancer or contractor to implement parts of a project. The core idea, the decision to build it in the first place, the design choices, the testing, and the overall direction still come from humans. Those parts require thought, effort, and ownership, and that deserves appreciation. Either way, I think projects like this are valuable for sparking curiosity and making technical ideas more approachable to common people, which is always a good thing.