node-inspector/v8-profiler
node bindings for the v8 profiler observed · 2026-08-28
Health v2 · maintenance only
23/100
- Activity 0
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 5754
- days_rel: n/a
- days_push: 2934
- n_releases_24m: 0
Adoption not part of the score
1125 stars · 129 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Node.js native bindings (C++) to the V8 profiler, exposing CPU profiling and heap snapshot APIs programmatically. It integrates with node-inspector for debugging and performance analysis of Node applications.
Use cases
- profile cpu usage of a node.js application
- take heap snapshots to find memory leaks
- compare two heap snapshots to detect memory growth
- export v8 cpu profiles for analysis in devtools
- adjust cpu profiler sampling interval
- integrate profiling into node-inspector
When to choose
- you need programmatic CPU or heap profiling in Node.js
- you are maintaining legacy code already using v8-profiler or node-inspector
When to avoid
- starting a new project - use the built-in inspector module or modern profilers
- you need actively maintained software with recent updates
- you need profiling for non-V8 runtimes
Facets
library · maturity abandoned
monitoring benchmarking developer-tools performance developer-tools backend cross-platform v8 cpu-profiling heap-snapshots native-addons profiling nodejs
1 source
- readme: https://github.com/node-inspector/v8-profiler · fetched 2026-08-28 · 23143d25054d
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| node-inspector/v8-profiler | main | 23 |
For agents
markdown · JSON · MCP: product_card(name="node-inspector/v8-profiler")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem