Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 20:37 UTC

sockjs / sockjs-node

WebSocket emulation - Node.js server

JavaScriptMIT★ 2,099 stars⑂ 306 forkssince Jul 2011View on GitHub ↗

sockjs/sockjs-node holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Community & Adoption (76/100) and lowest on Vitality (44/100). It was last updated 11 days ago. A single contributor accounts for most of its recent work.

65
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.

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

Ownership

SockJSOrganization
73 followers10 public repossince Aug 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmsockjs0.3.2456,768,491361749 days agowebsocketswebsocket

Metrics by category

Vitality

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

44Weak · 21% of overall
How it's scored
28.8/36Push recency — last push 11 days ago
3.5/36Commit cadence — 5/52 weeks with commits
9.4/18Commit volume — 10 commits in the last year
2/10OpenSSF Scorecard: Maintained — 2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year10
human_commit_share0.87
days_since_last_push11
active_weeks_last_year5
How it's scored
27/27Ships releases — 11 releases published
0/36Release recency — latest release 1,749 days ago
12.6/27Release cadence — a release every ~274.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count11
latest_release_tagv0.3.24
releases_from_tagsno
days_since_latest_release1,749
mean_days_between_releases274.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?

76Good · 17% of overall
How it's scored
53.9/60Stars — 2,099 stars
20.7/25Forks — 306 forks
9.6/15Watchers — 55 watchers
Inputs used
forks306
stars2,099
watchers55
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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 56,768,491 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessockjs
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads56,768,491
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.6/22.5Commit distribution — top contributor authored 62% of commits
13.5/13.5Contributor breadth — 36 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled36
top_contributor_share0.62
How it's scored
38.8/42Issue resolution — 92% of issues closed
19/30PR acceptance — 69/109 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 8/15 approved changesets -- score normalized to 5
Inputs used
merged_prs69
open_issues16
closed_issues194
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.924
closed_unmerged_prs40
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
13.4/25Owner reach — 73 followers of sockjs
19.6/25Track record — 10 public repos, account ~15 yr old
Inputs used
followers73
owner_typeOrganization
is_verifiedno
owner_loginsockjs
public_repos10
account_age_days5,505
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 1,749 days ago
20/20Version history — 36 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessockjs
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,749

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests — 8 out of 24 merged PRs checked by a CI test -- score normalized to 3
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 site — http://sockjs.org
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicssockjs, javascript, nodejs, node, websocket, real-time
has_wikino
homepagehttp://sockjs.org
docs_sitehttp://sockjs.org
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0.8/2.5CI-Tests — 8 out of 24 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 8/15 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 5 contributing companies or organizations
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
1.5/7.5Maintained — 2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: uuid 8.3.2 (high 7.5)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 147 days ago
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages6
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages1
Matched the npm:sockjs@0.3.24 runtime dependency closure — what installing the published package pulls in — 6 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.

48Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
9.2/40Legible commit history — 15 of 87 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.172
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.mjs
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 13 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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
toolchain_manifests—
dependency_bot_commit_share0.13
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/32 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes6,957
source_files_sampled32
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

2,099GitHub stars
36contributors
10commits, last 12 months
11days since last push
11releases
1bus factor
16open 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 ★ / 306 ⇿
0Stars
306Forks
11Releases

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.

012525037530352011-102019-032026-08
Major 0Minor 0Patch 11

Each point covers 14 days.

OpenSSF Scorecard 5.2 / 10
5.2aggregate

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-09-17 20:37 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
3CI-Tests8 out of 24 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 8/15 approved changesets -- score normalized to 5
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmdebug^4.3.1package.json
npmfaye-websocket^0.11.3package.json
All dependencies 90

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

RegistryPackageVersionRelation
npmdebug4.4.3direct
npmfaye-websocket0.11.3direct
npm@eslint-community/eslint-utils4.9.1indirect
npm@eslint-community/regexpp4.12.2indirect
npm@eslint/config-array0.23.5indirect
npm@eslint/config-helpers0.5.5indirect
npm@eslint/core1.2.1indirect
npm@eslint/js10.0.1indirect
npm@eslint/object-schema3.0.5indirect
npm@eslint/plugin-kit0.7.1indirect
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@pkgr/core0.2.9indirect
npm@types/esrecurse4.3.1indirect
npm@types/estree1.0.8indirect
npm@types/json-schema7.0.15indirect
npmacorn8.16.0indirect
npmacorn-jsx5.3.2indirect
npmajv6.15.0indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.7indirect
npmcross-spawn7.0.6indirect
npmdeep-is0.1.4indirect
npmescape-string-regexp4.0.0indirect
npmeslint10.3.0indirect
npmeslint-config-prettier10.1.8indirect
npmeslint-plugin-prettier5.5.5indirect
npmeslint-scope9.1.2indirect
npmeslint-visitor-keys3.4.3indirect
npmeslint-visitor-keys5.0.1indirect
npmespree11.2.0indirect
npmesquery1.7.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmexpress^4.16.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-diff1.3.0indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfile-entry-cache8.0.0indirect
npmfind-up5.0.0indirect
npmflat-cache4.0.1indirect
npmflatted3.4.2indirect
npmglob-parent6.0.2indirect
npmglobals17.6.0indirect
npmhapi^17.6.0indirect
npmhttp-parser-js0.5.2indirect
npmignore5.3.2indirect
npmimurmurhash0.1.4indirect
npminert^5.1.0indirect
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
npmkoa^2.5.3indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmminimatch10.2.5indirect
npmms2.1.3indirect
npmnatural-compare1.4.0indirect
npmnode-static^0.7.11indirect
npmoptionator0.9.4indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmprelude-ls1.2.1indirect
npmprettier3.8.3indirect
npmprettier-linter-helpers1.0.1indirect
npmpunycode2.3.1indirect
npmsafe-buffer5.2.1indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsockjs^0.4.0indirect
npmsynckit0.11.12indirect
npmtype-check0.4.0indirect
npmuri-js4.4.1indirect
npmwebsocket-driver0.7.5indirect
npmwebsocket-extensions0.1.4indirect
npmwebsocket-multiplex^0.1.0indirect
npmwhich2.0.2indirect
npmword-wrap1.2.5indirect
npmyocto-queue0.1.0indirect
Dependency advisories 1

Installing npm:sockjs@0.3.24 pulls in 6 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
uuid8.3.2directhigh113.0.1

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.