Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 23:01 UTC

software-mansion / rnrepo

A Repository for React Native Pre-Built Artifacts

TypeScript · Kotlin · AstroNo license detected★ 436 stars⑂ 13 forkssince Jun 2025View on GitHub ↗
KindLibraryWeb interfaceCommand-line toolhow this is determined

software-mansion/rnrepo holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (80/100) and lowest on Security (42/100). It was last updated today. A single contributor accounts for most of its recent work.

71
overall / 100
Good

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.

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

Ownership

Software MansionOrganization · verified domain
1,673 followers67 public repossince Oct 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@rnrepo/build-tools0.2.2152,2691240 days agococoapodsgradlereact-nativernrepoiosandroidpluginprebuildsxcframeworkaar
npm@rnrepo/expo-config-plugin0.3.6147,8821640 days agoreact-nativeexpoconfigpluginprebuildsrnrepo

Metrics by category

Vitality

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

56Moderate · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
28.4/36Commit cadence — 41/52 weeks with commits
18/18Commit volume — 354 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year354
human_commit_share0.92
days_since_last_push0
active_weeks_last_year41
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

55Moderate · 17% of overall
How it's scored
42.8/60Stars — 436 stars
9/25Forks — 13 forks
0/15Watchers — 1 watchers
Inputs used
forks13
stars436
watchers1
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes
How it's scored
73/80Monthly downloads — 300,151 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@rnrepo/build-tools, @rnrepo/expo-config-plugin
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads300,151
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?

80Excellent · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.3/22.5Commit distribution — top contributor authored 72% of commits
13.5/13.5Contributor breadth — 15 contributors
10/10OpenSSF Scorecard: Contributors — project has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.721
How it's scored
40.3/42Issue resolution — 96% of issues closed
27.3/30PR acceptance — 334/367 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs334
open_issues3
closed_issues72
prs_merged_7d1
prs_decided_7d3
prs_merged_30d2
prs_decided_30d4
issue_closed_ratio0.96
closed_unmerged_prs33
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
23.2/25Owner reach — 1,673 followers of software-mansion
25/25Track record — 67 public repos, account ~6 yr old
Inputs used
followers1,673
owner_typeOrganization
is_verifiedyes
owner_loginsoftware-mansion
public_repos67
account_age_days2,517

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on npm
35/35Publish recency — latest publish 40 days ago
20/20Version history — 16 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@rnrepo/build-tools, @rnrepo/expo-config-plugin
ecosystemsnpm
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows — 14 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.js
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

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — http://rnrepo.org/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttp://rnrepo.org/
docs_sitehttp://rnrepo.org/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

42Weak · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
4.5/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 7 contributing companies or organizations
0/10Dangerous-Workflow — dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
4.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
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 — 138 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.2
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://rnrepo.org/llms.txt)
40/40Legible commit history — 92 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://rnrepo.org/llms.txt
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — packages/build-tools/gradle-plugin/build.gradle (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — .eslintrc.js
11/11Static type checking — packages/expo-config-plugin/tsconfig.json, packages/website/tsconfig.json, tsconfig.json
0/10Reproducible environment
10/10Demonstrated agent practice — 16 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
9/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configspackages/expo-config-plugin/tsconfig.json, packages/website/tsconfig.json, tsconfig.json
agent_commit_share0.16
toolchain_manifestspackages/build-tools/gradle-plugin/build.gradle
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.3/55Manageable file sizes — 1/77 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes71,484
source_files_sampled77
oversized_source_files1

Key facts

436GitHub stars
15contributors
354commits, last 12 months
0days since last push
0releases
1bus factor
3open 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 436 stars today.
  • Could not fetch npm package '@rnrepo/builder' from its registry
  • Could not fetch npm package '@rnrepo/publisher' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 403 ★ / 13 ⇿
403Stars
13Forks

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.

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.

010020030040050040313822025-122026-042026-08
OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-12 23:00 UTC

9Binary-Artifactsbinaries present in source code
6Branch-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 7 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
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
0Vulnerabilities138 existing vulnerabilities detected
Direct dependencies 29
RegistryPackageVersion constraintManifest
npmcommander^13.1.0package.json
npmsemver^7.7.4package.json
npmzx^8.6.0package.json
npmcommander^13.1.0packages/builder/package.json
npm@rnrepo/configworkspace:*packages/builder/package.json
npmzx^8.6.0packages/builder/package.json
npm@rnrepo/configworkspace:*packages/database/package.json
npm@supabase/supabase-js^2.47.0packages/database/package.json
npm@expo/config-plugins*packages/expo-config-plugin/package.json
npm@expo/config-types*packages/expo-config-plugin/package.json
npm@rnrepo/build-tools0.2.2packages/expo-config-plugin/package.json
npm@octokit/rest^22.0.0packages/publisher/package.json
npm@rnrepo/configworkspace:*packages/publisher/package.json
npm@rnrepo/databaseworkspace:*packages/publisher/package.json
npmcommander^13.1.0packages/publisher/package.json
npmzx^8.6.0packages/publisher/package.json
npm@octokit/plugin-paginate-rest^14.0.0packages/scheduler/package.json
npm@octokit/rest^22.0.0packages/scheduler/package.json
npm@rnrepo/configworkspace:*packages/scheduler/package.json
npm@rnrepo/databaseworkspace:*packages/scheduler/package.json
npmsemver^7.7.3packages/scheduler/package.json
npm@rnrepo/databaseworkspace:*packages/website/package.json
npm@swmansion/ui-components^1.0.59packages/website/package.json
npmastro^4.16.6packages/website/package.json
npmlucide-astro^0.555.0packages/website/package.json
npmlucide-react^1.27.0packages/website/package.json
npmreact^18.3.1packages/website/package.json
npmreact-dom^18.3.1packages/website/package.json
npmshiki^3.17.1packages/website/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.