GitHub radar

Top 5 GitHub Repos This Week

This week the community doubled down on agentic tooling — from zero-trust IDEs to DAG orchestration runtimes to curriculum knowledge graphs. I kept stumbling across projects that treat model output as something to verify, not trust by default.

01withmarbleapp/os-taxonomy 2.8kJavaScript

I opened this expecting another AI toy and found a proper knowledge graph: 1,590 micro-topics mapped across 8 primary school subjects with 3,221 prerequisite dependencies, published by Marble (Generative Spark, Inc.). The licensing is unusually thorough — ODbL for the database layer, CC BY-SA for the authored content, with SHA-256 checksums and a CITATION.cff included. The interactive visualization at withmarble.com/curriculum is the clearest prerequisite map for K-8 learning I've seen, and the JSON schema is clean enough to slot directly into an RAG pipeline.

Why a vibe-coder should care

If you're building a tutoring agent or adaptive learning system, this is the prerequisite graph you'd otherwise spend months constructing manually.

Open on GitHub

I tried this Codex plugin on a reference photo of a desk lamp and was genuinely surprised — it runs through seven build passes (blockout → structural → refinement → materials → surfaces → lighting → interaction) and outputs pure TypeScript/Three.js geometry with no GLBs or downloaded assets. The quality gate uses AI vision to score the rendered output against the reference image before advancing to the next pass. The README makes an explicit design decision I respect: it does not do photogrammetry — it reconstructs the soul of the object, not its mesh, which means the result is actually usable in games and interactive scenes.

Why a vibe-coder should care

Generates animation-ready 3D hierarchies with correct pivots from a single image — useful for any AI product that needs procedural geometry without a dedicated art pipeline.

Open on GitHub

Clodex is a local-first Electron IDE that treats model output as untrusted input from the start — that design choice runs through the whole codebase. I set it up and the thing that immediately stood out is the Guardian system: sensitive operations like file writes and network calls require independent authorization rather than relying on the model's judgment. The agent runtime has proper turn management, cancellation, and recovery; memory is append-only with provenance tracking. They shipped the public preview with 3,322 tests passing.

Why a vibe-coder should care

The only agentic IDE I've seen that enforces a trust boundary between the model and the filesystem at the runtime level, not just through prompting.

Open on GitHub

This is a Claude Code skill that converts articles, data, and screenshots into labeled explanatory diagrams — text baked directly into the image, not a chart you have to style yourself afterward. I tested the chart beautification mode: feed it a screenshot of a messy spreadsheet and it reconstructs a clean material-design visualization with correct data. Supports 10+ diagram types including process flows, hierarchy maps, and scientific mechanisms. What impressed me most is the QA checklist in the README — it verifies label accuracy, data integrity, and readability at thumbnail scale before shipping.

Why a vibe-coder should care

Automates the hardest part of technical explanation design — turning abstract data into visually legible labeled diagrams without a designer in the loop.

Open on GitHub
05xiaotianfotos/homerail 491TypeScript

HomeRail converts one-off agent chats into reusable, auditable DAG workflows designed to run on a home server or a small datacenter node. I liked that the primary interface is voice-first — Chinese by default, with ASR/TTS/VAD all included — and the CLI is the fallback rather than the main path. The `hr dag supervise` command gives a real-time stream of DAG execution; `hr replay` lets you step backward through any run. Workers run in isolated Docker containers per DAG run, which means parallel workflows genuinely can't pollute each other's workspaces.

Why a vibe-coder should care

Proper infrastructure for running agents reliably at home — with audit trails and replay instead of hoping the chat context doesn't get lost.

Open on GitHub