Easy unit testing in node.js and the browser, based on the assert module.
Scores
The two headline scores, measured daily, with 30, 90, and 180 day views.
Jul 19, 2026
Current57
Previous1
Weekly average
Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.
180 observed daily rows. Missing days are not fabricated.
40% Hot today + 40% Hot this week + 20% Breakout.
Per-day formula: 0.40 × Hot today + 0.40 × Hot week + 0.20 × Breakout.
| Date | Stars | Stars 1d | Stars 7d | Stars 14d | Stars 30d | Stars 90d | Same-day multiplier | Weekly multiplier | Fortnight multiplier | Hot today | Hot week | Breakout | Stored score |
|---|
Jul 19, 2026
Current1
Previous1
Weekly average
Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.
180 observed daily rows. Missing days are not fabricated.
30% Continuity + 30% Closure + 20% Shipping + 10% Liveness + 10% Support burden.
Per-day formula: 0.30 × Continuity + 0.30 × Closure + 0.20 × Shipping + 0.10 × Liveness + 0.10 × Support burden.
Stars, issues, pull requests, and releases are daily observations. Pushed-days and license are repository snapshot-derived inputs and are not independent historical GitHub events.
| Date | Issues opened | Issues closed | PRs opened | PRs merged | Releases | Stars | Open issues | Pushed days ago | Continuity | Closure | Shipping | Liveness | Support burden | License | Observed days | Missing days | Needs healing | Stored score |
|---|
Reliability breakdown
Component scores measured daily from GitHub activity (2026-07-18).
Activity on 0 of 90 tracked days in the last 90 and 0 of 30 in the last 30.
Merged 0 of 0 PRs opened and closed 0 of 0 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.
0 releases in the last 180 days, 0 in the last 90 and 0 in the last 30 — a steady cadence scores highest.
Last push 1368 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).
Modeled — lower is better; concentration of commits in few maintainers. Contributors graph
Topics
Jump into the topic listings this repository belongs to.
Measured history
Weekly GitHub totals with 30, 90, and 180 day views.
Feb 22, 2026
Current0
Previous0
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
36 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Feb 22, 2026
Current0
Previous0
Weekly total
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
36 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Feb 22, 2026
Current0
Previous0
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
36 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Feb 22, 2026
Current0
Previous0
Weekly total
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
36 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Feb 22, 2026
Current0
Previous0
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
36 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
caolan/nodeunit is a unit testing framework for Node.js and browser JavaScript, designed around the built-in assert module. It provides a straightforward test structure, asynchronous test support, and simple reporting suitable for classic JavaScript projects. The framework is commonly used in older Node.js codebases and legacy test suites that predate newer testing tools.
Join the conversation
Share what you know about nodeunit — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Explain what worked, what broke down, and what another team should know before adopting nodeunit.
Project Q&A
Browse implementation threads tied directly to caolan/nodeunit. Each question links through to the full answer page.
Be the first to ask how teams run nodeunit in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses nodeunit — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post