⚡NexusPulse OS: The Edge-Native Truth Engine for Open Source

This is a submission for the DEV Weekend Challenge: Community

The Community

I built this for the Open Source Community—specifically for developers who are tired of "Star-Bait."

In our ecosystem, GitHub Stars are treated as the gold standard, but they are a lagging indicator. They tell you who was popular three years ago, not who is active today. Many "top-tier" libraries are actually Zombie Repos—abandoned by maintainers but still coasting on historical hype. NexusPulse OS provides a real-time "Vibe Check" so you can vet a dependency's health before it enters your package.json.

What I Built

NexusPulse OS is a high-performance "Vitality Engine." It strips away the vanity metrics and calculates a project's Vitality DNA by analyzing live signals directly from the global GitHub search index.

The Vitality Formula

The engine doesn't just count numbers; it weights them to reflect actual project health:

• Commits (x3.5 Weight): The Heartbeat. Measures raw activity velocity over a 30-day window.
• PRs Merged (x0.3 Weight): The Flow. High merge rates indicate a maintainer who is actively listening to the community.
• Stale Issues (-0.2 Penalty): The Debt. Stale issues act as a drag on the score, flagging projects that are drowning in their own backlog.

Demo

Check out the NexusPulse OS Live Dashboard

Code

bingkahu / nexuspulse-os

⚡ NexusPulse OS

The Repository Vitality Monitor Live App: nexuspulse-os.pages.dev

NexusPulse is a high-octane, edge-powered dashboard that turns raw GitHub data into a living "Vitality Score." Designed for the modern web, it provides a real-time pulse check on open-source health with zero latency.

🔮 What is Vitality?

In the world of code, static stars don't tell the full story. NexusPulse measures momentum. Our Vitality Engine analyzes:

• Pulse (Commit Velocity): Not just total commits, but the rhythm of activity over the last 30 days.
• Flow (PR Efficiency): How fast ideas are turning into merged code.
• Weight (Issue Health): Identifying "stale" blockers that are slowing the project down.
• Community: Real-time contributor tracking and star-to-fork ratios.

⚡ Built for the Edge

NexusPulse doesn't just display data; it lives on the edge.

• Blazing Fast: Hosted on nexuspulse-os.pages.dev via Cloudflare Pages for instant global delivery.
• Live Sync: Directly integrated with the GitHub Search API…

View on GitHub

How I Built It

This isn't a standard React app; it's an Edge-native architecture designed for global scale and zero latency.

⚡ The "Uncapped" Search Indexing

Most GitHub dashboards hit a "30-result wall" because they use standard REST endpoints. For high-velocity repos, that's a rounding error. I bypassed this by utilizing the GitHub Search API.

By querying the search index directly, NexusPulse aggregates uncapped activity counts in a single atomic request. This ensures 100% data accuracy for repos with 10,000+ monthly commits.

// Bypassing the 30-item REST limit via the Search API Index
const searchDate = thirtyDaysAgo.toISOString().split('T')[0];

const commitSearch = await fetch(
  `https://api.github.com/search/commits?q=repo:${owner}/${repo}+author-date:>=${searchDate}&per_page=1`,
  { 
    headers: { 
      'Authorization': `Bearer ${process.env.GITHUB_TOKEN}`,
      'Accept': 'application/vnd.github.v3+json'
    } 
  }
);

const data = await commitSearch.json();
// This returns the REAL global count (total_count) in one trip
const trueCommitCount = data.total_count;

The V8 Edge Runtime

The application logic is deployed to the V8 Edge Runtime (Cloudflare Pages).

• Global Distribution: The "Vitality Brain" runs in data centers physically closest to the user.
• Zero Cold Starts: Unlike traditional serverless functions, Edge runtimes are always warm, resulting in sub-100ms response times globally.

The Mascot State Machine

The UI features a reactive mascot that functions as a Visual State Machine. Its behavior is hard-coded to the Vitality Engine's output:

• Supernova State: High-energy, glowing animations for thriving projects.
• Recovering State: A "healing" visual state for projects bouncing back from a lull.
• Zombie State: Desaturated, stalling visuals for repos that have hit a dead end.

💡 The TypeScript Case Study

Even a titan like microsoft/typescript can dip into a "Recovering" state (as seen in my dashboard) when the commit-to-issue ratio shifts. This proves the engine catches real-time lulls that "Star Counts" completely ignore.

Reflection

Building for the Edge required a "Zero-Dependency" mindset. No heavy Node.js polyfills, no bloated middleware. The result is a lightning-fast tool that empowers the community to look past the stars and see the truth.

---

Tech Stack: Next.js 14 (App Router), Tailwind CSS, GitHub Search API, Cloudflare V8 Edge Runtime.

---

Have you ever been burned by "Star-Bait"?
Tell me about a time you added a high-star library only to realize it hadn't been updated in years.