Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-17 13:49 UTC

CoMPaTech / python-airos

Python module for Ubiquity airOS devices

PythonMIT★ 5 stars⑂ 5 forkssince Jul 2025View on GitHub ↗

CoMPaTech/python-airos holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Community & Adoption (42/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

TomPersonal account
26 followers79 public repossince Oct 2013CoMPa Technology

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIairos0.6.1330,018570 days agohomeautomationubiquitiuispairosmodule

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 0 days ago
35.3/36Commit cadence — 51/52 weeks with commits
18/18Commit volume — 195 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year195
human_commit_share0.38
days_since_last_push0
active_weeks_last_year51
How it's scored
16.2/27Ships releases — 46 version tags (no GitHub releases)
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~29.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count46
latest_release_tagv0.6.13
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases29.4
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?

42Weak · 17% of overall
How it's scored
9.8/60Stars — 5 stars
5/25Forks — 5 forks
0/15Watchers — 1 watchers
Inputs used
forks5
stars5
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges10
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, codecov.io, github.com, shields.io, sonarcloud.io
has_pull_request_templateno
How it's scored
59.7/80Monthly downloads — 30,018 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesairos
dependents—
ecosystemspypi
total_downloads—
monthly_downloads30,018
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.4/22.5Commit distribution — top contributor authored 98% of commits
5.4/13.5Contributor breadth — 4 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.984
How it's scored
23.4/42Issue resolution — 56% of issues closed
29.4/30PR acceptance — 260/265 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs260
open_issues4
closed_issues5
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.556
closed_unmerged_prs5
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
10.3/25Owner reach — 26 followers of CoMPaTech
25/25Track record — 79 public repos, account ~12 yr old
Inputs used
followers26
owner_typeUser
is_verified—
owner_loginCoMPaTech
public_repos79
account_age_days4,742
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 57 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesairos
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

82Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff], [tool.pylint])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://pypi.org/project/airos
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicsairos, home-assistant, home-automation, homeassistant, python, python3, ubiquiti, uisp
has_wikino
homepagehttps://pypi.org/project/airos
docs_sitehttps://pypi.org/project/airos
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

71Good · 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
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
5/5SAST — SAST tool is run on all commits
4.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages14
unassessed_packages3
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 14 resolved dependencies against OSV. 3 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

49Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
16.8/40Legible commit history — 12 of 38 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.316
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff], [tool.pylint])
11/11Static type checking — airos/py.typed, mypy.ini
0/10Reproducible environment
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 62 of the last 100 commits are automated dependency updates
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsairos/py.typed, mypy.ini
agent_commit_share0.02
toolchain_manifests—
dependency_bot_commit_share0.62
How it's scored
27/45Type-checkable code — Python with type-check config (airos/py.typed, mypy.ini)
55/55Manageable file sizes — 0/23 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes20,057
source_files_sampled23
oversized_source_files0

Key facts

5GitHub stars
4contributors
195commits, last 12 months
0days since last push
46releases
1bus factor
4open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:airos@0.6.13; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 5 ⇿
0Stars
5Forks
22Releases

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.

12345512025-082026-012026-06
Major 0Minor 3Patch 19
OpenSSF Scorecard 6.4 / 10
6.4aggregate

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-17 13:49 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/30 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
10SASTSAST tool is run on all commits
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
PyPIaiohttp>=3.8.0pyproject.toml
PyPImashumaro>=3.14.0pyproject.toml
All dependencies 17

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

RegistryPackageVersionRelation
PyPIaiohttp—direct
PyPIaiohttp3.14.5direct
PyPImashumaro—direct
PyPImashumaro3.23direct
PyPIaiofiles25.1.0indirect
PyPIaioresponses0.7.9indirect
PyPIcoverage7.16.2indirect
PyPImypy2.4.0indirect
PyPIpydantic2.14.1indirect
PyPIpylint4.1.3indirect
PyPIpytest9.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-cov7.1.0indirect
PyPIradon6.0.1indirect
PyPIruff0.17.1indirect
PyPIsetuptools—indirect
PyPItypes-aiofiles25.1.0.20260518indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 14 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 3 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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 — PyPI.