Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 00:32 UTC

rive-app / rive-nitro-react-native

Rive React Native - v2 built with Nitro

TypeScript · Kotlin · SwiftMIT★ 153 stars⑂ 14 forkssince May 2025View on GitHub ↗
KindLibraryCommand-line toolMobile applicationWeb interfacehow this is determined

rive-app/rive-nitro-react-native holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Security (49/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

RiveOrganization · verified domain
1,368 followers62 public repossince Dec 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@rive-app/react-native0.4.20383,9814424 days agoreact-nativeiosandroid

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
27.7/36Commit cadence — 40/52 weeks with commits
18/18Commit volume — 198 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year198
human_commit_share1
days_since_last_push2
active_weeks_last_year40

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 46 releases published
36/36Release recency — latest release 3 days ago
27/27Release cadence — a release every ~6.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count46
latest_release_tagv0.5.0-beta.4
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases6.3
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?

73Good · 17% of overall
How it's scored
35.4/60Stars — 153 stars
9.3/25Forks — 14 forks
5/15Watchers — 9 watchers
Inputs used
forks14
stars153
watchers9
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_badges8
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
74.5/80Monthly downloads — 383,981 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@rive-app/react-native
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads383,981
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
9/54Bus factor — 1 contributor(s) cover half of all commits
9/22.5Commit distribution — top contributor authored 60% of commits
9.5/13.5Contributor breadth — 7 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.601
How it's scored
39.6/42Issue resolution — 94% of issues closed
25.2/30PR acceptance — 242/288 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs242
open_issues4
closed_issues65
prs_merged_7d3
prs_decided_7d4
prs_merged_30d9
prs_decided_30d10
issue_closed_ratio0.942
closed_unmerged_prs46
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
22.5/25Owner reach — 1,368 followers of rive-app
25/25Track record — 62 public repos, account ~6 yr old
Inputs used
followers1,368
owner_typeOrganization
is_verifiedyes
owner_loginrive-app
public_repos62
account_age_days2,475

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 24 days ago
20/20Version history — 44 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@rive-app/react-native
ecosystemsnpm
any_deprecatedno
min_days_since_publish24

Engineering Quality

Are baseline engineering and documentation practices in place?

83Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js, eslint.config.mjs, package.json ("prettier")
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 28 out of 30 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
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?

49Weak · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.2/2.5CI-Tests — 28 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
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 — 30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
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
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 144 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

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.

73Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.swmansion.com/llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.swmansion.com/llms.txt
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — android/build.gradle, example/android/app/build.gradle, example/android/build.gradle (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — eslint.config.js, eslint.config.mjs, package.json ("prettier")
11/11Static type checking — expo-example/tsconfig.json, expo55-example/tsconfig.json, expo57-example/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
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
lockfilesGemfile.lock, yarn.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsexpo-example/tsconfig.json, expo55-example/tsconfig.json, expo57-example/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifestsandroid/build.gradle, example/android/app/build.gradle, example/android/build.gradle, rive-debug-utils/android/build.gradle
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.7/55Manageable file sizes — 2/352 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes2,228,925
source_files_sampled352
oversized_source_files2
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 — demos, example
Inputs used
example_dirsdemos, example
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

153GitHub stars
7contributors
198commits, last 12 months
2days since last push
46releases
1bus factor
4open issues
Maven, npm, RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 14 ⇿
0Stars
14Forks
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.

03581013151422025-112026-042026-09
Major 0Minor 3Patch 37
OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-13 00:32 UTC

9Binary-Artifactsbinaries present in source code
5Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests28 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities144 existing vulnerabilities detected
Direct dependencies 88
RegistryPackageVersion constraintManifest
npm@expo/vector-icons^15.0.3expo-example/package.json
npm@react-native-async-storage/async-storage^2.1.2expo-example/package.json
npm@react-native-picker/picker^2.11.4expo-example/package.json
npm@react-navigation/bottom-tabs^7.4.0expo-example/package.json
npm@react-navigation/elements^2.6.3expo-example/package.json
npm@react-navigation/native^7.1.8expo-example/package.json
npmexpo~54.0.20expo-example/package.json
npmexpo-constants~18.0.10expo-example/package.json
npmexpo-font~14.0.9expo-example/package.json
npmexpo-haptics~15.0.7expo-example/package.json
npmexpo-image~3.0.10expo-example/package.json
npmexpo-linking~8.0.8expo-example/package.json
npmexpo-router~6.0.13expo-example/package.json
npmexpo-screen-orientation~9.0.8expo-example/package.json
npmexpo-splash-screen~31.0.10expo-example/package.json
npmexpo-status-bar~3.0.8expo-example/package.json
npmexpo-symbols~1.0.7expo-example/package.json
npmexpo-system-ui~6.0.8expo-example/package.json
npmexpo-web-browser~15.0.8expo-example/package.json
npmreact19.1.0expo-example/package.json
npmreact-dom19.1.0expo-example/package.json
npmreact-native0.81.5expo-example/package.json
npmreact-native-gesture-handler2.29.1expo-example/package.json
npmreact-native-nitro-modules0.36.5expo-example/package.json
npmreact-native-reanimated4.1.5expo-example/package.json
npmreact-native-safe-area-context~5.6.0expo-example/package.json
npmreact-native-screens~4.16.0expo-example/package.json
npmreact-native-web~0.21.0expo-example/package.json
npmreact-native-worklets0.6.1expo-example/package.json
npmrive-debug-utilsworkspace:*expo-example/package.json
npm@expo/vector-icons^15.0.3expo55-example/package.json
npm@react-native-async-storage/async-storage^2.1.2expo55-example/package.json
npm@react-native-picker/picker^2.11.4expo55-example/package.json
npm@react-navigation/bottom-tabs^7.15.5expo55-example/package.json
npm@react-navigation/elements^2.6.3expo55-example/package.json
npm@react-navigation/native^7.1.33expo55-example/package.json
npmexpo^55.0.12expo55-example/package.json
npmexpo-constants~55.0.12expo55-example/package.json
npmexpo-font~55.0.4expo55-example/package.json
npmexpo-haptics~55.0.14expo55-example/package.json
npmexpo-image~55.0.8expo55-example/package.json
npmexpo-linking~55.0.11expo55-example/package.json
npmexpo-router~55.0.11expo55-example/package.json
npmexpo-screen-orientation~55.0.13expo55-example/package.json
npmexpo-splash-screen~55.0.6expo55-example/package.json
npmexpo-status-bar~55.0.5expo55-example/package.json
npmexpo-symbols~55.0.7expo55-example/package.json
npmexpo-system-ui~55.0.15expo55-example/package.json
npmexpo-web-browser~15.0.10expo55-example/package.json
npmreact19.2.0expo55-example/package.json
npmreact-dom19.2.0expo55-example/package.json
npmreact-native0.83.4expo55-example/package.json
npmreact-native-gesture-handler~2.29.0expo55-example/package.json
npmreact-native-nitro-modules0.36.5expo55-example/package.json
npmreact-native-reanimated4.2.1expo55-example/package.json
npmreact-native-safe-area-context~5.6.2expo55-example/package.json
npmreact-native-screens~4.23.0expo55-example/package.json
npmreact-native-web~0.21.0expo55-example/package.json
npmreact-native-worklets0.7.4expo55-example/package.json
npmrive-debug-utilsworkspace:*expo55-example/package.json
npm@react-native-async-storage/async-storage^2.1.2expo57-example/package.json
npm@react-native-picker/picker^2.11.4expo57-example/package.json
npm@react-navigation/bottom-tabs^7.15.5expo57-example/package.json
npm@react-navigation/elements^2.6.3expo57-example/package.json
npm@react-navigation/native^7.1.33expo57-example/package.json
npmexpo^57.0.4expo57-example/package.json
npmexpo-constants~57.0.3expo57-example/package.json
npmexpo-font~57.0.0expo57-example/package.json
npmexpo-haptics~57.0.0expo57-example/package.json
npmexpo-image~57.0.0expo57-example/package.json
npmexpo-linking~57.0.2expo57-example/package.json
npmexpo-router~57.0.4expo57-example/package.json
npmexpo-screen-orientation~57.0.0expo57-example/package.json
npmexpo-splash-screen~57.0.2expo57-example/package.json
npmexpo-status-bar~57.0.0expo57-example/package.json
npmexpo-system-ui~57.0.0expo57-example/package.json
npmexpo-web-browser~57.0.0expo57-example/package.json
npmreact19.2.3expo57-example/package.json
npmreact-dom19.2.3expo57-example/package.json
npmreact-native0.86.0expo57-example/package.json
npmreact-native-gesture-handler~2.32.0expo57-example/package.json
npmreact-native-nitro-modules0.36.5expo57-example/package.json
npmreact-native-reanimated4.5.0expo57-example/package.json
npmreact-native-safe-area-context~5.7.0expo57-example/package.json
npmreact-native-screens4.25.2expo57-example/package.json
npmreact-native-web~0.21.0expo57-example/package.json
npmreact-native-worklets0.10.0expo57-example/package.json
npmrive-debug-utilsworkspace:*expo57-example/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.