Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-10 12:00 UTC

mobxjs / mobx-state-tree

Full-featured reactive state management without the boilerplate

TypeScriptMIT★ 7,052 stars⑂ 638 forkssince Sep 2016View on GitHub ↗

mobxjs/mobx-state-tree holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (97/100) and lowest on Vitality (61/100). It was last updated 37 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

MobXOrganization
182 followers34 public repossince Feb 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmmobx-state-tree8.0.0846,51713737 days agomobxmobx-state-treepromisereactivefrpfunctional-reactive-programmingstate-management

Metrics by category

Vitality

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

61Moderate · 21% of overall
How it's scored
18/36Push recency — last push 37 days ago
5.5/36Commit cadence — 8/52 weeks with commits
11.5/18Commit volume — 18 commits in the last year
6/10OpenSSF Scorecard: Maintained — 7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year18
human_commit_share1
days_since_last_push37
active_weeks_last_year8
How it's scored
27/27Ships releases — 47 releases published
36/36Release recency — latest release 37 days ago
19.8/27Release cadence — a release every ~72.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count47
latest_release_tagv8.0.0
releases_from_tagsno
days_since_latest_release37
mean_days_between_releases72.5
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?

97Exceptional · 17% of overall
How it's scored
60/60Stars — 7,052 stars
23.4/25Forks — 638 forks
10.7/15Watchers — 86 watchers
Inputs used
forks638
stars7,052
watchers86
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
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_badges3
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, circleci.com, shields.io
has_pull_request_templateyes
How it's scored
79/80Monthly downloads — 846,517 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesmobx-state-tree
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads846,517
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?

76Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.4/22.5Commit distribution — top contributor authored 45% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 32 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled98
top_contributor_share0.447
How it's scored
38.6/42Issue resolution — 92% of issues closed
25.2/30PR acceptance — 663/790 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 13/30 approved changesets -- score normalized to 4
Inputs used
merged_prs663
open_issues97
closed_issues1,119
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.92
closed_unmerged_prs127
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
16.3/25Owner reach — 182 followers of mobxjs
23.2/25Track record — 34 public repos, account ~10 yr old
Inputs used
followers182
owner_typeOrganization
is_verifiedno
owner_loginmobxjs
public_repos34
account_age_days3,879

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 37 days ago
20/20Version history — 137 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmobx-state-tree
ecosystemsnpm
any_deprecatedno
min_days_since_publish37

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — package.json ("prettier")
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 13 out of 25 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://mobx-state-tree.js.org/
10/10Repository description
10/10Topics — 9 topics
0/10Wiki
Inputs used
topicsmobx-state-tree, mst, mobx, state-tree, redux, observable, snapshot, state-management, hacktoberfest
has_wikino
homepagehttps://mobx-state-tree.js.org/
docs_sitehttps://mobx-state-tree.js.org/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

64Moderate · 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
1.2/2.5CI-Tests — 13 out of 25 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 13/30 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 32 contributing companies or organizations
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
4.5/7.5Maintained — 7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file 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_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate5.5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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_packages1
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:mobx-state-tree@8.0.0 runtime dependency closure — what installing the published package pulls in — 1 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.

64Moderate · 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 — 97 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.97
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — package.json ("prettier")
11/11Static type checking — __tests__/tsconfig.json, tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesbun.lockb
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs__tests__/tsconfig.json, tsconfig.json
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.5/55Manageable file sizes — 1/113 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes77,500
source_files_sampled113
oversized_source_files1
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 — recipes
Inputs used
example_dirsrecipes
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

7,052GitHub stars
98contributors
18commits, last 12 months
37days since last push
47releases
2bus factor
97open 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 ★ / 638 ⇿
0Stars
638Forks
45Releases

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.

0125250375500625750635102016-102021-092026-08
Major 3Minor 7Patch 25

Each point covers 9 days.

OpenSSF Scorecard 5.5 / 10
5.5aggregate

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-10 11:59 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
5CI-Tests13 out of 25 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 13/30 approved changesets -- score normalized to 4
10Contributorsproject has 32 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
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
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmts-essentials^9.4.1package.json
All dependencies 28

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

RegistryPackageVersionRelation
npmts-essentials^9.4.1direct
npm@size-limit/preset-big-lib^5.0.3indirect
npm@types/bun^1.0.6indirect
npm@types/node^12.0.2indirect
npmconcat^1.0.3indirect
npmcoveralls^3.1.0indirect
npmcpr^3.0.1indirect
npmdocusaurus^1.14.0indirect
npmhusky^7.0.0indirect
npmlint-staged^11.1.2indirect
npmmobx^7.0.3indirect
npmprettier3.4.1indirect
npmrollup^2.18.1indirect
npmrollup-plugin-commonjs^10.0.0indirect
npmrollup-plugin-filesize^9.0.1indirect
npmrollup-plugin-node-resolve^5.0.0indirect
npmrollup-plugin-replace^2.1.0indirect
npmrollup-plugin-terser^6.1.0indirect
npmshx^0.3.2indirect
npmsize-limit^5.0.3indirect
npmts-node^8.10.2indirect
npmtslib^2.0.0indirect
npmtslint^6.1.3indirect
npmtslint-config-prettier^1.18.0indirect
npmtypedoc0.15.8indirect
npmtypedoc-plugin-markdown2.2.11indirect
npmtypescript^5.3.3indirect
npmyarn-deduplicate^3.1.0indirect
Dependency advisories 0

Installing npm:mobx-state-tree@8.0.0 pulls in 1 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.