Awesome Open Source

Sign in Create account

Build desktop apps with JavaScript and Node access

NW.js combines web app development patterns with direct Node.js integration for desktop-focused JavaScript projects.

16

Hotness score

41

Reliability score

41,184

Stars

over 14 years

Age

0

Published reviews

0

Questions

Weekly average

Full metrics details

Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.

180 observed daily rows. Missing days are not fabricated.

Hotness formula

40% Hot today + 40% Hot this week + 20% Breakout.

40% Hot today: 1
40% Hot this week: 37
20% Breakout: 40
Stars gained: 1d: 0
Stars gained: 7d: 3
Stars gained: 14d: 1
Stars gained: 30d: 1
Stars gained: 90d: 41184

Per-day formula: 0.40 × Hot today + 0.40 × Hot week + 0.20 × Breakout.

Same-day multiplier = stars 1d ÷ max(1, stars 7d ÷ 7)
Weekly multiplier = stars 7d ÷ max(1, stars 30d ÷ 30 × 7)
Fortnight multiplier = stars 14d ÷ max(1, stars 90d ÷ 90 × 14)
Hot today = clamp(70 × log-scale(stars 1d, 1000) + 30 × breakout-scale(same-day, 4))
Hot week = clamp(75 × log-scale(stars 7d, 5000) + 25 × breakout-scale(weekly, 3))
Breakout = clamp(35 × breakout-scale(same-day, 4) + 40 × breakout-scale(weekly, 3) + 25 × breakout-scale(fortnight, 2.5))

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

Weekly average

Full metrics details

Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.

180 observed daily rows. Missing days are not fabricated.

Reliability formula

30% Continuity + 30% Closure + 20% Shipping + 10% Liveness + 10% Support burden.

30% Continuity: 41
30% Closure: 42
20% Shipping: 0
10% Liveness: 100
10% Support burden: 57

Per-day formula: 0.30 × Continuity + 0.30 × Closure + 0.20 × Shipping + 0.10 × Liveness + 0.10 × Support burden.

Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
Shipping = 100 × (20% × release ratio 30d + 30% × release ratio 90d + 50% × release ratio 180d); ratios are releases ÷ 2, 6, and 12, capped at 1
Support burden = 100 − 2 × open issues per 1,000 stars
Liveness = 100 × exp(−pushed days ago ÷ 120)

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

Continuity30% of headline41

Activity on 0 of 90 tracked days in the last 90 and 0 of 30 in the last 30.

Closure30% of headline42

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%.

PRs merged (90d)PRs opened (90d)Issues closed (90d)Issues opened (90d)

Shipping20% of headline0

0 releases in the last 180 days, 0 in the last 90 and 0 in the last 30 — a steady cadence scores highest.

Liveness10% of headline100

Last push 1 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).

Support burden10% of headline57

888 open issues against 41,184 stars — about 22 open issues per 1,000 stars. Lighter backlogs score higher.

Open issues Stargazers

Adoption confidence60

Modeled — how confidently teams are adopting this repo. Stargazers

Maintenance quality40

Modeled from PR/issue responsiveness and upkeep signals. Activity pulse

Risk score45

Modeled — lower is better; adoption and continuity risk. Repository

Stays active (30d)42%

Modeled chance the repo stays active over 30 days. Activity pulse

Stays active (90d)50%

Modeled chance the repo stays active over 90 days. Activity pulse

Release rhythm (180d)0

Regularity of releases over the last 180 days. Releases

Maintainer bus risk (90d)57%

Modeled — lower is better; concentration of commits in few maintainers. Contributors graph

Weekly total

Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

45 observed daily rows. Missing days are not fabricated.

Date	Value

Weekly total

Full metrics details

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

45 observed daily rows. Missing days are not fabricated.

Date	Value

Weekly total

Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

45 observed daily rows. Missing days are not fabricated.

Date	Value

Weekly total

Full metrics details

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

45 observed daily rows. Missing days are not fabricated.

Date	Value

Weekly total

Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

45 observed daily rows. Missing days are not fabricated.

Date	Value

Daily ratio — a gap means nothing was opened that day

How this works: each day's value is issues closed that day ÷ issues opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more issues than arrived that day.

Full metrics details

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

10 observed daily rows. Missing days are not fabricated.

Per-day formula: issues closed that day ÷ issues opened that day; blank when nothing was opened (a gap, not a zero).

Date	Issues opened	Issues closed	Stored score

Daily ratio — a gap means nothing was opened that day

How this works: each day's value is pull requests closed that day ÷ pull requests opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more pull requests than arrived that day.

Full metrics details

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

2 observed daily rows. Missing days are not fabricated.

Per-day formula: pull requests closed that day ÷ pull requests opened that day; blank when nothing was opened (a gap, not a zero).

Date	PRs opened	PRs closed	Stored score

About Nw.js

NW.js is a JavaScript runtime focused on desktop app development with familiar web technologies. It is designed for developers who want to build application interfaces with HTML, CSS, and JavaScript while also calling Node.js modules directly from the DOM or Web Workers. That combination makes it notable for projects that want web-style development ergonomics without separating the frontend from local system capabilities. For JavaScript teams evaluating runtime options, NW.js stands out when desktop packaging and Node integration are central requirements.

Write a review Ask a question Write a post

Q&A No threads yet

Be the first to ask how teams run nw.js in production. Every question you post becomes a durable, searchable answer page other developers can find.

Ask the first question

Posts No topic-linked posts yet

Share how your team uses nw.js — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.

Write the first post

Get a weekly email with the hottest new projects in the Web Development and JavaScript world.

No Spam. Unsubscribe easily at any time.

Privacy | About | Terms | Follow Us On Twitter

Copyright 2018-2026 Awesome Open Source. All rights reserved.