Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-18 09:49 UTC

margelo / react-native-nitro-fetch

A super-fast network fetching library for React Native with prefetching support

C++MIT★ 910 stars⑂ 35 forkssince Sep 2025View on GitHub ↗
KindNetwork serviceWeb interfacehow this is determined

margelo/react-native-nitro-fetch holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (90/100) and lowest on Security (37/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

MargeloOrganization
835 followers39 public repossince Oct 2021

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

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
17.3/36Commit cadence25/52 weeks with commits
18/18Commit volume174 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year174
human_commit_share
days_since_last_push0
active_weeks_last_year25

Release discipline

100Exceptional
How it's scored
27/27Ships releases25 releases published
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~7.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count25
latest_release_tagv1.5.1
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases7.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?

74Good · 17% of overall
How it's scored
48/60Stars910 stars
12.8/25Forks35 forks
2.7/15Watchers4 watchers
Inputs used
forks35
stars910
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
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
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.5/22.5Commit distributiontop contributor authored 71% of commits
13.5/13.5Contributor breadth15 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.713
How it's scored
31/42Issue resolution74% of issues closed
25.5/30PR acceptance90/106 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 7/30 approved changesets -- score normalized to 2
Inputs used
merged_prs90
open_issues10
closed_issues28
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.737
closed_unmerged_prs16
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
21/25Owner reach835 followers of margelo
21.2/25Track record39 public repos, account ~4 yr old
Inputs used
followers835
owner_typeOrganization
is_verified
owner_loginmargelo
public_repos39
account_age_days1,746
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests17 out of 17 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://fetch.margelo.com
10/10Repository description
10/10Topics10 topics
0/10Wiki
Inputs used
topicscronet, fast, fetch, http, http2, network, nitro, prefetch, react, react-native
has_wikino
homepagehttps://fetch.margelo.com
docs_sitehttps://fetch.margelo.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

37Weak · 16% of overall
How it's scored
6.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests17 out of 17 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
1.5/7.5Code-ReviewFound 7/30 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 11 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities61 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.7
Excluded from scoring (no data or not applicable): Packaging, 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.

48Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.mjs
11/11Static type checkingdocs-website/tsconfig.json, example/tsconfig.json, packages/react-native-nitro-fetch/expo/plugins/tsconfig.json, packages/react-native-nitro-fetch/tsconfig.json, packages/react-native-nitro-text-decoder/tsconfig.json, packages/react-native-nitro-websockets/expo/plugins/tsconfig.json, packages/react-native-nitro-websockets/tsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock, package-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsdocs-website/tsconfig.json, example/tsconfig.json, packages/react-native-nitro-fetch/expo/plugins/tsconfig.json, packages/react-native-nitro-fetch/tsconfig.json, packages/react-native-nitro-text-decoder/tsconfig.json, packages/react-native-nitro-websockets/expo/plugins/tsconfig.json, packages/react-native-nitro-websockets/tsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC++ (statically typed)
53.6/55Manageable file sizes4/157 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes2,815,929
source_files_sampled157
oversized_source_files4
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examplesexample
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

910GitHub stars
15contributors
174commits, last 12 months
0days since last push
25releases
1bus factor
10open issues
npm, RubyGemspackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.7 / 10
3.7aggregate

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

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests17 out of 17 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 7/30 approved changesets -- score normalized to 2
10Contributorsproject has 11 contributing companies or organizations
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
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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
0Vulnerabilities61 existing vulnerabilities detected
Direct dependencies 33
RegistryPackageVersion constraintManifest
npm@docusaurus/core3.9.2docs-website/package.json
npm@docusaurus/preset-classic3.9.2docs-website/package.json
npm@mdx-js/react^3.0.0docs-website/package.json
npmclsx^2.0.0docs-website/package.json
npmprism-react-renderer^2.3.0docs-website/package.json
npmreact^19.0.0docs-website/package.json
npmreact-dom^19.0.0docs-website/package.json
RubyGemscocoapods>= 1.13example/Gemfile
RubyGemsactivesupport>= 6.1.7.5example/Gemfile
RubyGemsxcodeproj< 1.26.0example/Gemfile
RubyGemsconcurrent-ruby< 1.3.4example/Gemfile
RubyGemsbigdecimalexample/Gemfile
RubyGemsloggerexample/Gemfile
RubyGemsbenchmarkexample/Gemfile
RubyGemsmutex_mexample/Gemfile
RubyGemsnkfexample/Gemfile
npm@dr.pogodin/react-native-fs^2.0.0example/package.json
npm@react-navigation/bottom-tabs^7.15.5example/package.json
npm@react-navigation/native^7.1.33example/package.json
npm@react-navigation/native-stack^7.14.5example/package.json
npmreact19.2.3example/package.json
npmreact-native0.86.0example/package.json
npmreact-native-harness^1.0.0-alpha.25example/package.json
npmreact-native-nitro-fetch../packages/react-native-nitro-fetchexample/package.json
npmreact-native-nitro-modules^0.36.1example/package.json
npmreact-native-nitro-text-decoder../packages/react-native-nitro-text-decoderexample/package.json
npmreact-native-nitro-websockets../packages/react-native-nitro-websocketsexample/package.json
npmreact-native-safe-area-context^5.7.0example/package.json
npmreact-native-screens^4.24.0example/package.json
npmreact-native-worklets^0.9.0example/package.json
npmexpress^4.21.2test-server/package.json
npmmulter^2.0.1test-server/package.json
npmws^8.18.0test-server/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.12.0 — full methodology · metrics wiki.

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