Public record
Software health reportschema 0.18.0 · metrics 2.10.0 · 2026-07-21 12:20 UTC

nodejs / citgm

Canary in the Gold Mine

JavaScriptCustom license★ 604 stars⑂ 154 forkssince Jul 2015View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

nodejs/citgm holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (84/100) and lowest on AI Readiness (32/100). It was last updated 3 days ago. 2 contributors account for most of its recent work.

81
overall / 100
Excellent

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.

81
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 69 is calibrated to 81 on the published index scale (record calibration 2026-08-02).

Ownership

Node.jsOrganization
16,207 followers231 public repossince Nov 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmcitgm10.0.28612286 days ago

Metrics by category

Vitality

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

64Moderate · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
2.8/36Commit cadence4/52 weeks with commits
11.3/18Commit volume17 commits in the last year
3/10OpenSSF Scorecard: Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year17
human_commit_share
days_since_last_push3
active_weeks_last_year4
How it's scored
16.2/27Ships releases100 version tags (no GitHub releases)
36/36Release recencylatest release 6 days ago
19.8/27Release cadencea release every ~99.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv10.0.2
releases_from_tagsyes
days_since_latest_release6
mean_days_between_releases99.6
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

74Good · 17% of overall
How it's scored
45.1/60Stars604 stars
18.2/25Forks154 forks
8.4/15Watchers33 watchers
Inputs used
forks154
stars604
watchers33
growth_stateorganic
growth_factor_pct100

Community health

94Exceptional
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
39.1/80Monthly downloads861 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagescitgm
dependents
ecosystemsnpm
total_downloads
monthly_downloads861
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?

84Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.8/22.5Commit distributiontop contributor authored 30% of commits
13.5/13.5Contributor breadth67 contributors
10/10OpenSSF Scorecard: Contributorsproject has 91 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled67
top_contributor_share0.297
How it's scored
35.9/42Issue resolution86% of issues closed
21.7/30PR acceptance531/733 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 17/23 approved changesets -- score normalized to 7
Inputs used
merged_prs531
open_issues49
closed_issues288
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.855
closed_unmerged_prs202
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach16,207 followers of nodejs
25/25Track record231 public repos, account ~11 yr old
Inputs used
followers16,207
owner_typeOrganization
is_verified
owner_loginnodejs
public_repos231
account_age_days4,255
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 6 days ago
20/20Version history228 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagescitgm
ecosystemsnpm
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

69Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests8 out of 17 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://www.npmjs.com/package/citgm
10/10Repository description
10/10Topics6 topics
0/10Wiki
Inputs used
topicsnodejs, test, npm-module, mit, javascript, node
has_wikino
homepagehttps://www.npmjs.com/package/citgm
docs_sitehttps://www.npmjs.com/package/citgm
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

55Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1/2.5CI-Tests8 out of 17 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 17/23 approved changesets -- score normalized to 7
2.5/2.5Contributorsproject has 91 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
2.2/7.5Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packagingno data
2.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities70 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages33
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 1 resolved dependencies against OSV. 33 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

32At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.js
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/64 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes9,655
source_files_sampled64
oversized_source_files0

Key facts

604GitHub stars
67contributors
17commits, last 12 months
3days since last push
100releases
2bus factor
49open issues
npmpackage ecosystems

Data collection warnings

  • deps.dev does not index npm:citgm@10.0.2; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 604 ★ / 154 ⇿
604Stars
154Forks

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.

0125250375500625604143432015-072021-012026-06

Each point covers 11 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-07-21 12:20 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
4CI-Tests8 out of 17 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 17/23 approved changesets -- score normalized to 7
10Contributorsproject has 91 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities70 existing vulnerabilities detected
Direct dependencies 24
RegistryPackageVersion constraintManifest
npm@npmcli/package-json^7.0.0package.json
npmasync^3.2.6package.json
npmbl^6.1.3package.json
npmchalk^5.6.2package.json
npmcolumnify^1.6.0package.json
npmexeca^9.6.0package.json
npmlodash^4.17.21package.json
npmnormalize-git-url^3.0.2package.json
npmnpm-package-arg^13.0.0package.json
npmnpm-which^3.0.1package.json
npmpnpm^10.15.1package.json
npmroot-check^2.0.0package.json
npmsemver^7.7.2package.json
npmstrip-ansi^7.1.2package.json
npmsupports-color^10.2.2package.json
npmtar^7.4.3package.json
npmuid-number0.0.6package.json
npmundici^7.16.0package.json
npmwhich^5.0.0package.json
npmwinston^3.17.0package.json
npmxml-sanitizer^2.0.2package.json
npmxmlbuilder^15.1.1package.json
npmyargs^18.0.0package.json
npmyarn^1.22.22package.json
All dependencies 34

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

RegistryPackageVersionRelation
npm@npmcli/package-json^7.0.0direct
npmasync^3.2.6direct
npmbl^6.1.3direct
npmchalk^5.6.2direct
npmcolumnify^1.6.0direct
npmexeca^9.6.0direct
npmlodash^4.17.21direct
npmnormalize-git-url^3.0.2direct
npmnpm-package-arg^13.0.0direct
npmnpm-which^3.0.1direct
npmpnpm^10.15.1direct
npmroot-check^2.0.0direct
npmsemver^7.7.2direct
npmstrip-ansi^7.1.2direct
npmsupports-color^10.2.2direct
npmtar^7.4.3direct
npmuid-number0.0.6direct
npmundici^7.16.0direct
npmwhich^5.0.0direct
npmwinston^3.17.0direct
npmxml-sanitizer^2.0.2direct
npmxmlbuilder^15.1.1direct
npmyargs^18.0.0direct
npmyarn^1.22.22direct
npm@eslint/js^9.35.0indirect
npmansi-regex^6.2.2indirect
npmeslint^9.35.0indirect
npmeslint-config-prettier^10.1.8indirect
npmglobals^16.4.0indirect
npmprettier^3.6.2indirect
npmstring-to-stream^3.0.1indirect
npmtap^21.1.0indirect
npmtap-parser^18.0.0indirect
npmxml2js^0.6.2indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 33 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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.18.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.