Awesome Open Source logo
Awesome Open Source
Sign in Create account

c4milo/node-webkit-agent

NodeJS agent for WebKit devtools front-end

4
Hotness score
9
Reliability score
1,094
Stars
over 14 years
Age
0
Published reviews
0
Questions

Scores

Hotness and reliability

The two headline scores, measured daily, with 30, 90, and 180 day views.

Hotness score

Jul 19, 2026

Current4

Previous6

Weekly average

100500
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: 1
  • 20% Breakout: 1
  • Stars gained: 1d: 0
  • Stars gained: 7d: 0
  • Stars gained: 14d: 1
  • Stars gained: 30d: 2
  • Stars gained: 90d: 2

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))
DateStarsStars 1dStars 7dStars 14dStars 30dStars 90dSame-day multiplierWeekly multiplierFortnight multiplierHot todayHot weekBreakoutStored score

Reliability score

Jul 19, 2026

Current9

Previous9

Weekly average

100500
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: 5
  • 30% Closure: 0
  • 20% Shipping: 0
  • 10% Liveness: 0
  • 10% Support burden: 73

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.

DateIssues openedIssues closedPRs openedPRs mergedReleasesStarsOpen issuesPushed days agoContinuityClosureShippingLivenessSupport burdenLicenseObserved daysMissing daysNeeds healingStored score

Reliability breakdown

What drives the reliability score

Component scores measured daily from GitHub activity (2026-07-19).

Continuity30% of headline5

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

Activity pulse
Closure30% of headline0

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.

Releases
Liveness10% of headline0

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

Repository
Support burden10% of headline73

Open-issue load isn't tracked for this repo yet.

Open issuesStargazers
Adoption confidence2

Modeled — how confidently teams are adopting this repo. Stargazers

Maintenance quality9

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

Risk score78

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

Stays active (30d)0%

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

Stays active (90d)2%

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)95%

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

Topics

Explore related topics

Jump into the topic listings this repository belongs to.

JavascriptRemote DebuggingCpu Profiling

Measured history

Project metrics

Weekly GitHub totals with 30, 90, and 180 day views.

Weekly star gains

Jul 19, 2026

Current0

Previous1

Weekly star gains

110
Full metrics details

GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.

180 observed daily rows. Missing days are not fabricated.

DateValue

Cumulative stars

Jul 19, 2026

Current1,094

Previous1,094

Cumulative total

1,0945470
Full metrics details

Running total of the GitHub GraphQL stargazer count over time (not weekly deltas), reconstructed from starredAt events and totalCount in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.

180 observed daily rows. Missing days are not fabricated.

DateValue

Issues opened

Jul 19, 2026

Current0

Previous0

Weekly total

110
Full metrics details

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

179 observed daily rows. Missing days are not fabricated.

DateValue

Issues closed

Jul 19, 2026

Current0

Previous0

Weekly total

110
Full metrics details

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

179 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests opened

Jul 19, 2026

Current0

Previous0

Weekly total

110
Full metrics details

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

179 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests closed

Jul 19, 2026

Current0

Previous0

Weekly total

110
Full metrics details

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

179 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests merged

Jul 19, 2026

Current0

Previous0

Weekly total

110
Full metrics details

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

179 observed daily rows. Missing days are not fabricated.

DateValue

About Node Webkit Agent

c4milo/node-webkit-agent is an open source project centered on a Node.js agent that connects to the WebKit DevTools front-end. In a JavaScript workflow, it fits the profiling and runtime analysis layer, where teams need consistent behavior across local development and automation. It is commonly used when teams need repeatable visibility into runtime costs before prioritizing optimization work.

Adoption decisions should focus on compatibility with your runtime, framework, and existing tooling, plus the cost of introducing new conventions. A practical rollout is to pilot it in one repository or package, capture agreed defaults, and then expand through scripts or CI once the workflow proves stable. That phased approach keeps disruption low while making long-term maintenance expectations explicit.

Join the conversation

Reviews · Questions · Posts

Share what you know about node-webkit-agent — write a review from your real experience, ask an implementation question, or publish a post about how you use it.

Write a review Ask a question Write a post

Share your experience

Write or update your review

Explain what worked, what broke down, and what another team should know before adopting node-webkit-agent.

Sign in to review Create account

Write your review now — it saves locally and publishes automatically after you sign in.

Rating
Positive attributes
Negative attributes

Project Q&A

Questions and answers

Browse implementation threads tied directly to c4milo/node-webkit-agent. Each question links through to the full answer page.

Q&A No threads yet

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

Ask the first question

Related posts

Posts tagged with the same topics

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.

Posts No topic-linked posts yet

Share how your team uses node-webkit-agent — 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 Node.js and Node Webkit Agent world.
No Spam. Unsubscribe easily at any time.
Privacy | About | Terms | Follow Us On Twitter

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