Skip to content
gitdebt

nodejs/is-my-node-vulnerable

Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.

Open on GitHub
Current stars
327
Activity since
2023
Latest activity
Jan 2026

Public star activity

Last 30 days
+4
Last 90 days
+5
Actions / day
0.3
Public star actions
stars from January 22, 2023 to January 31, 2026, peaking at 300.300 STARS3 YR300JAN 2026JAN 2023

300 stars on January 31, 2026.

stars by date
Datestars
January 22, 20232
January 26, 202322
January 27, 202323
January 30, 202324
February 2, 202325
February 4, 202328
February 5, 202329
February 21, 202343
February 22, 202346
February 23, 202347
March 4, 202348
March 9, 202351
March 10, 202352
March 14, 202353
March 15, 202354
March 16, 202355
March 20, 202356
March 21, 202357
March 22, 202358
March 29, 202359
April 8, 202360
April 17, 202361
April 27, 202362
June 21, 202363
July 2, 202364
July 22, 202365
July 27, 202366
July 28, 202368
July 29, 202369
August 7, 202370
October 20, 202373
October 21, 202377
October 24, 202378
November 3, 202379
November 7, 202380
November 11, 202381
November 17, 202382
February 11, 202483
February 16, 202496
February 17, 202499
February 18, 2024102
February 19, 2024104
February 22, 2024105
February 25, 2024106
February 27, 2024107
February 28, 2024108
March 8, 2024109
March 12, 2024113
March 19, 2024114
April 1, 2024115
April 3, 2024116
April 4, 2024118
April 5, 2024119
April 16, 2024120
April 17, 2024121
May 6, 2024122
May 31, 2024123
July 20, 2024124
September 17, 2024125
September 18, 2024126
September 26, 2024127
October 18, 2024140
October 19, 2024152
October 20, 2024154
October 21, 2024159
October 22, 2024163
October 23, 2024179
October 24, 2024186
October 25, 2024191
October 28, 2024192
October 30, 2024193
November 1, 2024194
November 2, 2024198
November 3, 2024199
November 4, 2024200
November 5, 2024201
November 6, 2024202
November 11, 2024204
November 12, 2024205
November 13, 2024208
November 15, 2024209
November 19, 2024210
December 10, 2024211
December 14, 2024212
December 23, 2024221
December 26, 2024222
January 3, 2025224
January 7, 2025227
January 16, 2025229
January 17, 2025237
January 18, 2025239
January 20, 2025240
January 21, 2025241
January 22, 2025244
January 23, 2025246
January 27, 2025247
January 29, 2025249
January 30, 2025251
January 31, 2025252
February 1, 2025254
February 4, 2025256
February 5, 2025257
February 6, 2025262
February 7, 2025265
February 9, 2025268
February 10, 2025272
February 11, 2025275
February 13, 2025276
February 17, 2025277
February 25, 2025278
February 26, 2025279
March 12, 2025280
March 29, 2025281
April 12, 2025282
April 23, 2025283
May 1, 2025284
May 6, 2025285
May 7, 2025286
June 6, 2025287
June 11, 2025288
June 22, 2025289
July 16, 2025290
July 21, 2025291
July 26, 2025292
August 2, 2025293
August 8, 2025294
October 19, 2025295
November 7, 2025296
January 9, 2026297
January 20, 2026298
January 30, 2026299
January 31, 2026300

The last 90 days run behind its lifetime average, which is ordinary for a mature project.

Observed activity milestones: 100 around Feb 2024

The commit history reads nodejs/is-my-node-vulnerable a second time

methodology

Fix-labelled changes, file change frequency, ownership concentration and maintenance cadence, each computed from this repository's analyzed commit window. None of them is derived from stars, which is why they are allowed to disagree with the curve above.

Fix-labelled changes
Fix-labelled changes for nodejs/is-my-node-vulnerable
File change frequency
File change frequency for nodejs/is-my-node-vulnerable
Bus factor
Bus factor for nodejs/is-my-node-vulnerable
Maintenance pulse
Maintenance pulse for nodejs/is-my-node-vulnerable
Contributors
Contributors for nodejs/is-my-node-vulnerable
Language activity
Language activity for nodejs/is-my-node-vulnerable
Commit activity
Commit activity for nodejs/is-my-node-vulnerable
Recent TODO/FIXME movement
Recent TODO/FIXME movement for nodejs/is-my-node-vulnerable

Attention is not adoption.

Stars against usage

No published package was detected for this repository, so there is nothing to lay over star growth.

Earned badges

badge studio

Maintenance, ownership and star-momentum signals, computed from the same commit and star history and embeddable as static images.

Reading badge evidence for nodejs/is-my-node-vulnerable.

Notes on nodejs/is-my-node-vulnerable

How many stars does nodejs/is-my-node-vulnerable have?
GitHub currently reports 327 stars for nodejs/is-my-node-vulnerable. The chart itself is rebuilt from historical star data, which records star actions and not unstars, so it reads as an attention signal rather than a net star count.
What does recent star activity look like for is-my-node-vulnerable?
gitdebt observed about 5 public star actions for nodejs/is-my-node-vulnerable over the latest 90 days of archive coverage (about 4 in the latest 30). This is an approximate attention signal, not a net-star count, because unstars are not present. That's below its lifetime average activity pace, which is common for mature projects.
Is is-my-node-vulnerable still active?
Public archive data shows about 4 star actions for nodejs/is-my-node-vulnerable in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
When was is-my-node-vulnerable created?
nodejs/is-my-node-vulnerable was created on January 20, 2023. The first public star activity observed for nodejs/is-my-node-vulnerable is from Jan 2023.

Read is-my-node-vulnerable against a neighbour

comparison builder
Compare with any repository

Put this drawing in your README

markdown for agents

The block below publishes the chart with its source and coverage date stated beside it — the same three facts the title block above shows, as text a reader can check. The prompt underneath hands a coding agent the badges and repo-health charts as well.

README.md · nodejs/is-my-node-vulnerable star history
<a href="https://gitdebt.com/nodejs/is-my-node-vulnerable?ref=readme">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/nodejs/is-my-node-vulnerable/chart.svg?theme=dark" />
    <img alt="nodejs/is-my-node-vulnerable star history" src="https://api.gitdebt.com/api/repos/nodejs/is-my-node-vulnerable/chart.svg?theme=light" />
  </picture>
</a>

<sub>Star history source: Historical star data · Covers through January 31, 2026 · Still updating — <a href="https://gitdebt.com/nodejs/is-my-node-vulnerable?ref=readme">gitdebt</a></sub>

Light and dark variants, alt text, and one provenance line. Provenance is text in your README, never baked into the image URL, so the chart stays cacheable.

Paste it into Claude Code, Cursor, Codex, or any coding agent with your checkout open. It carries the measured numbers, the exact snippets, and the rules — including replacing an existing star-history widget in place rather than stacking a second chart under it.