Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 04:22 UTC

blueconic / node-oom-heapdump

Create a V8 heap snapshot right before an "Out of Memory" error occurs, or create a heap snapshot or CPU profile on request.

JavaScript · C++MIT★ 109 stars⑂ 12 forkssince Sep 2017View on GitHub ↗

blueconic/node-oom-heapdump holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (70/100) and lowest on AI Readiness (44/100). It was last updated 22 days ago. A single contributor accounts for most of its recent work.

73
overall / 100
Good

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

73
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 64 is calibrated to 73 on the published index scale (record calibration 2026-08-02).

Ownership

BlueConicOrganization · verified domain
14 followers13 public repossince Nov 2013

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmnode-oom-heapdump3.8.83,9966322 days agonodejsmemory-leakout-of-memoryheapdumpmemoryonfatalerroronoomerror

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

70Good · 21% of overall
How it's scored
28.8/36Push recency — last push 22 days ago
7.6/36Commit cadence — 11/52 weeks with commits
13/18Commit volume — 27 commits in the last year
8/10OpenSSF Scorecard: Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year27
human_commit_share0.95
days_since_last_push22
active_weeks_last_year11
How it's scored
27/27Ships releases — 52 releases published
36/36Release recency — latest release 22 days ago
27/27Release cadence — a release every ~22.1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count52
latest_release_tag3.8.8
releases_from_tagsno
days_since_latest_release22
mean_days_between_releases22.1

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

50Moderate · 17% of overall
How it's scored
33/60Stars — 109 stars
8.7/25Forks — 12 forks
1.7/15Watchers — 3 watchers
Inputs used
forks12
stars109
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
48/80Monthly downloads — 3,996 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesnode-oom-heapdump
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads3,996
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.3/22.5Commit distribution — top contributor authored 81% of commits
6.8/13.5Contributor breadth — 5 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.808
How it's scored
42/42Issue resolution — 100% of issues closed
21.7/30PR acceptance — 21/29 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/20 approved changesets -- score normalized to 0
Inputs used
merged_prs21
open_issues0
closed_issues20
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs8
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
8.5/25Owner reach — 14 followers of blueconic
20.3/25Track record — 13 public repos, account ~12 yr old
Inputs used
followers14
owner_typeOrganization
is_verifiedyes
owner_loginblueconic
public_repos13
account_age_days4,722

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 22 days ago
20/20Version history — 63 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesnode-oom-heapdump
ecosystemsnpm
any_deprecatedno
min_days_since_publish22

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 4 out of 6 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 10 topics
0/10Wiki
Inputs used
topicsnodejs, memory-leak, out-of-memory, heap-dump, memory-snapshot, heap-size, devtools-protocol, memory, cpu-profiling, cpu-profile
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

67Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1.5/2.5CI-Tests — 4 out of 6 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/20 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
6/7.5Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
4/5SAST — SAST tool is not run on all commits -- score normalized to 8
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages28
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:node-oom-heapdump@3.8.8 runtime dependency closure — what installing the published package pulls in — 28 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

44Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
17.4/40Legible commit history — 31 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.326
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.js
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 5 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.05
toolchain_manifests—
dependency_bot_commit_share0.01
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/10 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes5,675
source_files_sampled10
oversized_source_files0

Key facts

109GitHub stars
5contributors
27commits, last 12 months
22days since last push
52releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 12 ⇿
0Stars
12Forks
36Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0246810121212018-052022-072026-09
Major 2Minor 10Patch 24

Each point covers 8 days.

OpenSSF Scorecard 5.9 / 10
5.9aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-10-21 04:22 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
6CI-Tests4 out of 6 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/20 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
8SASTSAST tool is not run on all commits -- score normalized to 8
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
npm@mapbox/node-pre-gyp2.0.3package.json
npmbindings^1.5.0package.json
npmchrome-remote-interface^0.34.0package.json
npmnan^2.27.0package.json
npmrequire-main-filename^2.0.0package.json
npmws^8.21.0package.json
All dependencies 98

Full resolved dependency set from the GitHub dependency graph: 7 direct and 91 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@mapbox/node-pre-gyp2.0.3direct
npmbindings1.5.0direct
npmchrome-remote-interface0.34.0direct
npmnan2.27.0direct
npmrequire-main-filename2.0.0direct
npmws7.5.11direct
npmws8.21.0direct
npm@aashutoshrathi/word-wrap1.2.6indirect
npm@eslint-community/eslint-utils4.9.1indirect
npm@eslint-community/regexpp4.12.2indirect
npm@eslint/config-array0.23.2indirect
npm@eslint/config-helpers0.5.2indirect
npm@eslint/core1.1.0indirect
npm@eslint/object-schema3.0.2indirect
npm@eslint/plugin-kit0.6.0indirect
npm@humanfs/core0.19.2indirect
npm@humanfs/node0.16.8indirect
npm@humanfs/types0.15.0indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/retry0.4.3indirect
npm@isaacs/fs-minipass4.0.1indirect
npm@types/esrecurse4.3.1indirect
npm@types/estree1.0.8indirect
npm@types/json-schema7.0.15indirect
npmabbrev2.0.0indirect
npmacorn8.16.0indirect
npmacorn-jsx5.3.2indirect
npmagent-base7.1.3indirect
npmajv6.14.0indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.12indirect
npmchownr3.0.0indirect
npmcommander2.11.0indirect
npmconsola3.2.3indirect
npmcross-spawn7.0.6indirect
npmdebug4.3.3indirect
npmdeep-is0.1.4indirect
npmdetect-libc2.0.2indirect
npmescape-string-regexp4.0.0indirect
npmeslint10.0.1indirect
npmeslint-config-google0.14.0indirect
npmeslint-scope9.1.1indirect
npmeslint-visitor-keys3.4.3indirect
npmeslint-visitor-keys5.0.1indirect
npmespree11.1.1indirect
npmesquery1.7.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfile-entry-cache8.0.0indirect
npmfile-uri-to-path1.0.0indirect
npmfind-up5.0.0indirect
npmflat-cache4.0.1indirect
npmflatted3.4.2indirect
npmglob-parent6.0.2indirect
npmhttps-proxy-agent7.0.6indirect
npmignore5.3.2indirect
npmimurmurhash0.1.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmisexe2.0.0indirect
npmjson-buffer3.0.1indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv4.5.4indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmlru-cache6.0.0indirect
npmminimatch10.2.4indirect
npmminipass7.1.2indirect
npmminizlib3.1.0indirect
npmms2.1.2indirect
npmnatural-compare1.4.0indirect
npmnode-fetch2.6.7indirect
npmnopt8.0.0indirect
npmoptionator0.9.3indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmprelude-ls1.2.1indirect
npmpunycode2.3.1indirect
npmsemver7.5.4indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmtar7.5.22indirect
npmtr460.0.3indirect
npmtype-check0.4.0indirect
npmuri-js4.4.1indirect
npmwebidl-conversions3.0.1indirect
npmwhatwg-url5.0.0indirect
npmwhich2.0.2indirect
npmyallist4.0.0indirect
npmyallist5.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:node-oom-heapdump@3.8.8 pulls in 28 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.