Public record
Software health reportschema 0.23.0 · metrics 2.10.0 · 2026-07-21 15:51 UTC

INAVFlights / inav-configurator

JavaScript · HTMLGPL-3.0★ 727 stars⑂ 0 forkssince Mar 2026View on GitHub ↗

INAVFlights/inav-configurator holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on AI Readiness (65/100) and lowest on Security (19/100). It was last updated 126 days ago. 3 contributors account for most of its recent work.

45
overall / 100
Weak

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.

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

Ownership

INAVFlightOrganization
0 followers2 public repossince Mar 2026

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?

57Moderate · 21% of overall
How it's scored
9.9/36Push recencylast push 126 days ago
13.2/36Commit cadence19/52 weeks with commits
18/18Commit volume316 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year316
human_commit_share1
days_since_last_push126
active_weeks_last_year19
How it's scored
27/27Ships releases84 releases published
27/36Release recencylatest release 126 days ago
27/27Release cadencea release every ~0 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count84
latest_release_taguntagged-58a74ccc453672f866b7
releases_from_tagsno
days_since_latest_release126
mean_days_between_releases0

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

56Moderate · 17% of overall
How it's scored
46.4/60Stars727 stars
0/25Forks0 forks
14.6/15Watchers420 watchers
Inputs used
forks0
stars727
watchers420
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonwindow_too_short
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

42Weak · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
16.8/22.5Commit distributiontop contributor authored 25% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 8 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled100
top_contributor_share0.254
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptanceno decided pull requests or no data
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
0/25Owner reach0 followers of INAVFlights
4.2/25Track record2 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verified
owner_loginINAVFlights
public_repos2
account_age_days139
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
10/10Topics6 topics
10/10Wiki
Inputs used
topicsaircraft, drones, hacktoberfest, inav, inav-configurator, uav
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

19Critical · 16% of overall
How it's scored
3.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 8 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
0/7.5Maintained0 commit(s) and 0 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/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities83 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate1.9
Excluded from scoring (no data or not applicable): CI-Tests, Packaging. 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.

65Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md, js/transpiler/CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history85 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.85
agent_instruction_filesCLAUDE.md, js/transpiler/CLAUDE.md
agent_instruction_max_bytes5,925
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice5 of the last 100 commits agent-authored or agent-credited
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_testsyes
lockfilesyarn.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.05
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
54.3/55Manageable file sizes3/237 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes187,643
source_files_sampled237
oversized_source_files3
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
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

727GitHub stars
100contributors
316commits, last 12 months
126days since last push
84releases
3bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Could not fetch npm package 'inav-configurator' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 727 ★ / 0 ⇿
727Stars
84Releases

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.

2503755006257507263202026-032026-032026-03
Major 8Minor 11Patch 26
OpenSSF Scorecard 1.9 / 10
1.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-07-21 15:51 UTC

5Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 8 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities83 existing vulnerabilities detected
Direct dependencies 30
RegistryPackageVersion constraintManifest
npmacorn^8.14.0package.json
npm@electron/remote^2.1.3package.json
npmbrowserify-fs^1.0.0package.json
npmchart.js^4.4.1package.json
npmd3^7.9.0package.json
npmelectron-squirrel-startup^1.0.1package.json
npmelectron-store^10.1.0package.json
npmelectron-window-state^5.0.3package.json
npmfs0.0.1-securitypackage.json
npmi18next^25.5.0package.json
npminflection^3.0.2package.json
npmjbox^1.3.3package.json
npmjquery^3.7.1package.json
npmjquery-ui-dist1.13.3package.json
npmjquery-textcomplete^1.8.5package.json
npmmarked^16.2.1package.json
npmminimist^1.2.8package.json
npmmonaco-editor^0.54.0package.json
npmnouislider^15.8.1package.json
npmol^10.6.1package.json
npmpromise-map-series^0.3.0package.json
npmsemver^7.7.2package.json
npmserialport^13.0.0package.json
npmsmalltalk^4.1.2package.json
npmtemp^0.9.4package.json
npmthree^0.180.0package.json
npmthrottle-debounce^5.0.2package.json
npmusb^2.16.0package.json
npmwnumb^1.2.0package.json
npmxml2js^0.6.2package.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.23.0 — full methodology · metrics wiki.

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