Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 15:09 UTC

FHIR / sushi

SUSHI (aka "SUSHI Unshortens Short Hand Inputs") is a reference implementation command-line interpreter/compiler for FHIR Shorthand (FSH).

TypeScriptApache-2.0★ 188 stars⑂ 65 forkssince Oct 2019View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

FHIR/sushi holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Vitality (79/100) and lowest on Engineering Quality (66/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

FHIROrganization
188 followers60 public repossince Nov 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmfsh-sushi3.20.147,26311630 days ago

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
11.8/36Commit cadence17/52 weeks with commits
14.5/18Commit volume40 commits in the last year
9/10OpenSSF Scorecard: Maintained10 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year40
human_commit_share1
days_since_last_push0
active_weeks_last_year17
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 30 days ago
19.8/27Release cadencea release every ~46 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv3.20.1
releases_from_tagsno
days_since_latest_release30
mean_days_between_releases46
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?

75Good · 17% of overall
How it's scored
36.9/60Stars188 stars
15.1/25Forks65 forks
7.1/15Watchers20 watchers
Inputs used
forks65
stars188
watchers20
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/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_templateyes
How it's scored
62.3/80Monthly downloads47,263 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesfsh-sushi
dependents
ecosystemsnpm
total_downloads
monthly_downloads47,263
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?

78Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.7/22.5Commit distributiontop contributor authored 30% of commits
13.5/13.5Contributor breadth37 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled37
top_contributor_share0.3
How it's scored
35.1/42Issue resolution84% of issues closed
29.2/30PR acceptance913/938 decided PRs merged
10.8/13Newcomer PR acceptance5/6 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 19/30 approved changesets -- score normalized to 6
Inputs used
merged_prs913
open_issues115
closed_issues580
prs_merged_7d2
prs_decided_7d3
prs_merged_30d5
prs_decided_30d6
issue_closed_ratio0.835
closed_unmerged_prs25
first_time_authors_30d4
first_time_prs_merged_30d5
first_time_prs_decided_30d6
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
16.4/25Owner reach188 followers of FHIR
25/25Track record60 public repos, account ~12 yr old
Inputs used
followers188
owner_typeOrganization
is_verifiedno
owner_loginFHIR
public_repos60
account_age_days4,678

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 30 days ago
20/20Version history116 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesfsh-sushi
ecosystemsnpm
any_deprecatedno
min_days_since_publish30

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
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?

68Good · 16% of overall
How it's scored
6.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 19/30 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 4 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
6.8/7.5Maintained10 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 9
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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
3/7.5Vulnerabilities6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6
Excluded from scoring (no data or not applicable): Branch-Protection, 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
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages146
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:fsh-sushi@3.20.1 runtime dependency closure — what installing the published package pulls in — 146 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.

79Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history82 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.82
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes7,267
How it's scored
12.6/18One-command bootstrapantlr/build.gradle (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format configeslint.config.mjs
11/11Static type checkingtest/tsconfig.json, tsconfig.json
0/10Reproducible environment
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstest/tsconfig.json, tsconfig.json
agent_commit_share0.02
toolchain_manifestsantlr/build.gradle
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
51.5/55Manageable file sizes18/281 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes548,795
source_files_sampled281
oversized_source_files18
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

188GitHub stars
37contributors
40commits, last 12 months
0days since last push
100releases
2bus factor
115open issues
Maven, 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 ★ / 65 ⇿
0Stars
65Forks
100Releases

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.

01325385063756432019-112023-042026-09
Major 3Minor 39Patch 46

Each point covers 7 days.

OpenSSF Scorecard 6.0 / 10
6.0aggregate

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-18 15:09 UTC

9Binary-Artifactsbinaries present in source code
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
10CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 19/30 approved changesets -- score normalized to 6
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
9Maintained10 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 9
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 23
RegistryPackageVersion constraintManifest
npmajv^8.17.1package.json
npmantlr4^4.13.2package.json
npmaxios^1.15.0package.json
npmchalk^4.1.2package.json
npmcommander^13.1.0package.json
npmfhir-package-loader^2.2.3package.json
npmfhir-tool^5.0.2package.json
npmfs-extra^11.3.3package.json
npmhtml-minifier-terser5.1.1package.json
npmhttps-proxy-agent^7.0.5package.json
npmini^5.0.0package.json
npmjunk^3.1.0package.json
npmlodash^4.18.1package.json
npmreadline-sync^1.4.10package.json
npmsanitize-filename^1.6.4package.json
npmsax^1.6.0package.json
npmsemver^7.7.4package.json
npmtemp^0.9.4package.json
npmtext-table^0.2.0package.json
npmtitle-case^3.0.3package.json
npmvalid-url^1.0.9package.json
npmwinston^3.19.0package.json
npmyaml^1.10.2package.json
All dependencies 62

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

RegistryPackageVersionRelation
npmajv^8.17.1direct
npmantlr4^4.13.2direct
npmaxios^1.15.0direct
npmchalk^4.1.2direct
npmcommander^13.1.0direct
npmfhir-package-loader^2.2.3direct
npmfhir-tool^5.0.2direct
npmfs-extra^11.3.3direct
npmhtml-minifier-terser5.1.1direct
npmhttps-proxy-agent^7.0.5direct
npmini^5.0.0direct
npmjunk^3.1.0direct
npmlodash^4.18.1direct
npmreadline-sync^1.4.10direct
npmsanitize-filename^1.6.4direct
npmsax^1.6.0direct
npmsemver^7.7.4direct
npmtemp^0.9.4direct
npmtext-table^0.2.0direct
npmtitle-case^3.0.3direct
npmvalid-url^1.0.9direct
npmwinston^3.19.0direct
npmyaml^1.10.2direct
npm@eslint/eslintrc^3.3.5indirect
npm@eslint/js^10.0.1indirect
npm@types/fs-extra^11.0.4indirect
npm@types/html-minifier-terser5.1.1indirect
npm@types/ini^4.1.1indirect
npm@types/jest^30.0.0indirect
npm@types/json-diff^1.0.3indirect
npm@types/lodash^4.17.24indirect
npm@types/node^22.19.17indirect
npm@types/opener^1.4.3indirect
npm@types/readline-sync^1.4.8indirect
npm@types/sax^1.2.7indirect
npm@types/semver^7.7.1indirect
npm@types/temp^0.9.4indirect
npm@types/text-table^0.2.5indirect
npm@types/valid-url^1.0.7indirect
npm@typescript-eslint/eslint-plugin^8.58.2indirect
npm@typescript-eslint/parser^8.58.2indirect
npmacorn^8.14.1indirect
npmcopyfiles^2.4.1indirect
npmdel-cli^6.0.0indirect
npmdiff^9.0.0indirect
npmdiff2html-cli^5.2.15indirect
npmeslint^10.2.0indirect
npmeslint-config-prettier^10.1.8indirect
npmhl7.fhir.r4.core4.0.1indirect
npmhl7.fhir.us.core3.1.0indirect
npmhl7.fhir.uv.vhdircurrentindirect
npmjest^30.3.0indirect
npmjest-extended^7.0.0indirect
npmjest-mock-extended^4.0.0indirect
npmjson-diff^1.0.6indirect
npmnock^14.0.12indirect
npmopener^1.5.2indirect
npmprettier^3.8.3indirect
npmtar^7.5.22indirect
npmts-jest^29.4.9indirect
npmts-node^10.9.2indirect
npmtypescript^5.9.3indirect
Dependency advisories 0

Installing npm:fsh-sushi@3.20.1 pulls in 146 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 statisticsnpm.