Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-04 20:53 UTC

remarkjs / react-markdown

Markdown component for React

JavaScriptMIT★ 15,831 stars⑂ 920 forkssince May 2015View on GitHub ↗

remarkjs/react-markdown holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (95/100) and lowest on AI Readiness (23/100). It was last updated 470 days ago. 2 contributors account for most of its recent work.

60
overall / 100
Moderate

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.

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

Ownership

remarkOrganization
321 followers58 public repossince Dec 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmreact-markdown10.1.0111,098,82798515 days agoastcommonmarkcomponentgfmmarkdownreactreact-componentremarkunified

Metrics by category

Vitality

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

25At Risk · 21% of overall
How it's scored
0/36Push recencylast push 470 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push470
active_weeks_last_year0
How it's scored
27/27Ships releases21 releases published
7.2/36Release recencylatest release 515 days ago
19.8/27Release cadencea release every ~79.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count21
latest_release_tag10.1.0
releases_from_tagsno
days_since_latest_release515
mean_days_between_releases79.8
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?

95Exceptional · 17% of overall
How it's scored
60/60Stars15,831 stars
24.7/25Forks920 forks
9.7/15Watchers56 watchers
Inputs used
forks920
stars15,831
watchers56
growth_stateorganic
growth_factor_pct100

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
80/80Monthly downloads111,098,827 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesreact-markdown
dependents
ecosystemsnpm
total_downloads
monthly_downloads111,098,827
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?

75Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.6/22.5Commit distributiontop contributor authored 49% of commits
13.5/13.5Contributor breadth64 contributors
10/10OpenSSF Scorecard: Contributorsproject has 56 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled64
top_contributor_share0.486
How it's scored
42/42Issue resolution100% of issues closed
17.3/30PR acceptance118/205 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 8/30 approved changesets -- score normalized to 2
Inputs used
merged_prs118
open_issues1
closed_issues730
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.999
closed_unmerged_prs87
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 backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
18/25Owner reach321 followers of remarkjs
24.9/25Track record58 public repos, account ~10 yr old
Inputs used
followers321
owner_typeOrganization
is_verified
owner_loginremarkjs
public_repos58
account_age_days3,885
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
14/35Publish recencylatest publish 515 days ago
20/20Version history98 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesreact-markdown
ecosystemsnpm
any_deprecatedno
min_days_since_publish515

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://remarkjs.github.io/react-markdown/
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsmarkdown, commonmark, gfm, react, remark
has_wikino
homepagehttps://remarkjs.github.io/react-markdown/
docs_sitehttps://remarkjs.github.io/react-markdown/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 8/30 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 56 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
0/7.5Maintained0 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.8
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
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_packages81
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:react-markdown@10.1.0 runtime dependency closure — what installing the published package pulls in — 81 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.

23At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
9.6/40Legible commit history18 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.18
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
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_testsno
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codeJavaScript with type-check config (tsconfig.json)
55/55Manageable file sizes0/4 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes35,114
source_files_sampled4
oversized_source_files0

Key facts

15,831GitHub stars
64contributors
0commits, last 12 months
470days since last push
21releases
2bus factor
1open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-21: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 15831 stars today.

More detail

Star and fork history 15,814 ★ / 920 ⇿
15,814Stars
920Forks
21Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-21. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

04,0008,00012,00016,00015,814908522015-052020-122026-07
Major 5Minor 3Patch 13

Each point covers 11 days.

OpenSSF Scorecard 4.8 / 10
4.8aggregate

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-08-04 20:52 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 8/30 approved changesets -- score normalized to 2
10Contributorsproject has 56 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
npm@types/hast^3.0.0package.json
npm@types/mdast^4.0.0package.json
npmdevlop^1.0.0package.json
npmhast-util-to-jsx-runtime^2.0.0package.json
npmhtml-url-attributes^3.0.0package.json
npmmdast-util-to-hast^13.0.0package.json
npmremark-parse^11.0.0package.json
npmremark-rehype^11.0.0package.json
npmunified^11.0.0package.json
npmunist-util-visit^5.0.0package.json
npmvfile^6.0.0package.json
All dependencies 32

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

RegistryPackageVersionRelation
npm@types/hast^3.0.0direct
npm@types/mdast^4.0.0direct
npmdevlop^1.0.0direct
npmhast-util-to-jsx-runtime^2.0.0direct
npmhtml-url-attributes^3.0.0direct
npmmdast-util-to-hast^13.0.0direct
npmremark-parse^11.0.0direct
npmremark-rehype^11.0.0direct
npmunified^11.0.0direct
npmunist-util-visit^5.0.0direct
npmvfile^6.0.0direct
npm@testing-library/react^16.0.0indirect
npm@types/node^22.0.0indirect
npm@types/react^19.0.0indirect
npm@types/react-dom^19.0.0indirect
npmc8^10.0.0indirect
npmconcat-stream^2.0.0indirect
npmesbuild^0.25.0indirect
npmeslint-plugin-react^7.0.0indirect
npmglobal-jsdom^26.0.0indirect
npmprettier^3.0.0indirect
npmreact^19.0.0indirect
npmreact-dom^19.0.0indirect
npmrehype-raw^7.0.0indirect
npmrehype-starry-night^2.0.0indirect
npmremark-cli^12.0.0indirect
npmremark-gfm^4.0.0indirect
npmremark-preset-wooorm^11.0.0indirect
npmremark-toc^9.0.0indirect
npmtype-coverage^2.0.0indirect
npmtypescript^5.0.0indirect
npmxo^0.60.0indirect
Dependency advisories 0

Installing npm:react-markdown@10.1.0 pulls in 81 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.31.0 — full methodology · metrics wiki.

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