Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 18:38 UTC

mopsicus / shardy

Framework for online games and applications on Node.js

TypeScript · JavaScriptMIT★ 13 stars⑂ 0 forkssince Oct 2024View on GitHub ↗

mopsicus/shardy holds a health index of 10 out of 100, placing it in the Critical band. It scores highest on Vitality (65/100) and lowest on Security (26/100). It was last updated 14 days ago. A single contributor accounts for most of its recent work.

10
overall / 100
Critical

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.

10
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 50 is calibrated to 50 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 20% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

IgorPersonal account
143 followers46 public repossince Mar 2016

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmshardy1.4.1412714 days agoshardymicroserviceframeworkrpcwebnetcodegamesenginenetworkingmultiplayerwebsocketrealtimeserversockettypescriptnodejs

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
28.8/36Push recency — last push 14 days ago
2.1/36Commit cadence — 3/52 weeks with commits
11.5/18Commit volume — 18 commits in the last year
10/10OpenSSF Scorecard: Maintained — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year18
human_commit_share1
days_since_last_push14
active_weeks_last_year3
How it's scored
27/27Ships releases — 3 releases published
36/36Release recency — latest release 14 days ago
12.6/27Release cadence — a release every ~255.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv1.4.0
releases_from_tagsno
days_since_latest_release14
mean_days_between_releases255.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?

48Weak · 17% of overall
How it's scored
17.5/60Stars — 13 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars13
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
34.9/80Monthly downloads — 412 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesshardy
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads412
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?

39Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/27 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
15.5/25Owner reach — 143 followers of mopsicus
24.2/25Track record — 46 public repos, account ~10 yr old
Inputs used
followers143
owner_typeUser
is_verified—
owner_loginmopsicus
public_repos46
account_age_days3,864
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 14 days ago
20/20Version history — 7 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesshardy
ecosystemsnpm
any_deprecatedno
min_days_since_publish14

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 16 topics
10/10Wiki
Inputs used
topicsengine, framework, games, microservice, multiplayer, netcode, networking, nodejs, realtime, rpc, server, shardy, socket, typescript, web, websocket
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

26At Risk · 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/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/27 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.7
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier20
security_posture_after_multiplier7
security_posture_before_jurisdiction37
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 20% multiplier and gives Security posture an At risk ceiling of 34.

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_packages30
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:shardy@1.4.1 runtime dependency closure — what installing the published package pulls in — 30 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 23 of 27 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.852
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
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 27
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/33 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes23,599
source_files_sampled33
oversized_source_files0

Key facts

13GitHub stars
1contributors
18commits, last 12 months
14days since last push
3releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 3.7 / 10
3.7aggregate

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-20 18:38 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/27 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmwinston^3.19.0package.json
npmws^8.22.0package.json
All dependencies 130

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

RegistryPackageVersionRelation
npmwinston3.19.0direct
npmws8.22.0direct
npm@cacheable/memory2.2.0indirect
npm@cacheable/utils2.5.0indirect
npm@colors/colors1.6.0indirect
npm@colors/colors1.6.1indirect
npm@dabh/diagnostics2.0.9indirect
npm@eslint-community/eslint-utils4.10.1indirect
npm@eslint-community/regexpp4.12.2indirect
npm@eslint/config-array0.23.5indirect
npm@eslint/config-helpers0.7.0indirect
npm@eslint/core1.2.1indirect
npm@eslint/js10.0.1indirect
npm@eslint/object-schema3.0.5indirect
npm@eslint/plugin-kit0.7.3indirect
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@keyv/bigmap1.3.1indirect
npm@keyv/serialize1.1.1indirect
npm@so-ric/colorspace1.1.6indirect
npm@types/esrecurse4.3.1indirect
npm@types/estree1.0.9indirect
npm@types/json-schema7.0.15indirect
npm@types/node24.19.1indirect
npm@types/triple-beam1.3.5indirect
npm@types/ws8.18.2indirect
npm@typescript-eslint/eslint-plugin8.71.0indirect
npm@typescript-eslint/parser8.71.0indirect
npm@typescript-eslint/project-service8.71.0indirect
npm@typescript-eslint/scope-manager8.71.0indirect
npm@typescript-eslint/tsconfig-utils8.71.0indirect
npm@typescript-eslint/type-utils8.71.0indirect
npm@typescript-eslint/types8.71.0indirect
npm@typescript-eslint/typescript-estree8.71.0indirect
npm@typescript-eslint/utils8.71.0indirect
npm@typescript-eslint/visitor-keys8.71.0indirect
npmacorn8.18.0indirect
npmacorn-jsx5.3.2indirect
npmajv6.15.0indirect
npmasync3.2.6indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.12indirect
npmcacheable2.5.0indirect
npmcolor5.0.3indirect
npmcolor-convert3.1.3indirect
npmcolor-name2.1.1indirect
npmcolor-string2.1.4indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdeep-is0.1.4indirect
npmenabled2.0.0indirect
npmescape-string-regexp4.0.0indirect
npmeslint10.12.0indirect
npmeslint-config-prettier10.1.8indirect
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
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfdir6.5.0indirect
npmfecha4.2.3indirect
npmfile-entry-cache11.1.5indirect
npmfind-up5.0.0indirect
npmflat-cache6.1.23indirect
npmflatted3.4.4indirect
npmfn.name1.1.0indirect
npmglob-parent6.0.2indirect
npmhashery1.5.1indirect
npmhookified1.15.1indirect
npmhookified2.2.0indirect
npmignore5.3.2indirect
npmignore7.0.12indirect
npmimurmurhash0.1.4indirect
npminherits2.0.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-stream2.0.1indirect
npmisexe2.0.0indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv5.6.0indirect
npmkuler2.0.0indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmlogform2.7.0indirect
npmminimatch10.2.6indirect
npmms2.1.3indirect
npmnatural-compare1.4.0indirect
npmone-time1.0.0indirect
npmoptionator0.9.4indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpicomatch4.0.7indirect
npmprelude-ls1.2.1indirect
npmprettier3.9.9indirect
npmpunycode2.3.1indirect
npmqified0.10.1indirect
npmreadable-stream3.6.2indirect
npmsafe-buffer5.2.1indirect
npmsafe-stable-stringify2.5.0indirect
npmsemver7.8.5indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmstack-trace0.0.10indirect
npmstring_decoder1.3.0indirect
npmtext-hex1.0.0indirect
npmtinyglobby0.2.17indirect
npmtriple-beam1.4.1indirect
npmts-api-utils2.5.0indirect
npmtype-check0.4.0indirect
npmtypescript5.9.3indirect
npmtypescript-eslint8.71.0indirect
npmundici-types7.24.6indirect
npmuri-js4.4.1indirect
npmutil-deprecate1.0.2indirect
npmwhich2.0.2indirect
npmwinston-transport4.9.0indirect
npmword-wrap1.2.5indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:shardy@1.4.1 pulls in 30 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.