Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-19 20:49 UTC

astronomer / airflow-chart

A Helm chart to install Apache Airflow on Kubernetes

PythonCustom license★ 297 stars⑂ 95 forkssince Jan 2020View on GitHub ↗

astronomer/airflow-chart holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Vitality (94/100) and lowest on Security (59/100). It was last updated 4 days ago. 2 contributors account for most of its recent work.

93
overall / 100
Exceptional

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.

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

Ownership

AstronomerOrganization
800 followers354 public repossince May 2015

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?

94Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
25.6/36Commit cadence37/52 weeks with commits
18/18Commit volume103 commits in the last year
10/10OpenSSF Scorecard: Maintained21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year103
human_commit_share
days_since_last_push4
active_weeks_last_year37

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 4 days ago
27/27Release cadencea release every ~5.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv1.18.4
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases5.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?

68Good · 17% of overall
How it's scored
40.1/60Stars297 stars
16.4/25Forks95 forks
8.9/15Watchers41 watchers
Inputs used
forks95
stars297
watchers41
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes

Sustainability & Governance

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

82Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.6/22.5Commit distributiontop contributor authored 48% of commits
13.5/13.5Contributor breadth51 contributors
10/10OpenSSF Scorecard: Contributorsproject has 16 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled51
top_contributor_share0.485
How it's scored
42/42Issue resolution100% of issues closed
26.3/30PR acceptance613/700 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs613
open_issues0
closed_issues41
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs87
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
20.9/25Owner reach800 followers of astronomer
25/25Track record354 public repos, account ~11 yr old
Inputs used
followers800
owner_typeOrganization
is_verified
owner_loginastronomer
public_repos354
account_age_days4,084
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 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
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics6 topics
0/10Wiki
Inputs used
topicshelm-chart, airflow, apache-airflow, kubernetes, astronomer-software, astro-private-cloud
has_wikino
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?

59Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests30 out of 30 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
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 16 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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
3/7.5Vulnerabilities6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

65Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes2,733
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config
0/11Static type checking
10/10Reproducible environmentdevcontainer, Dockerfile, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontaineryes
has_linter_configyes
typecheck_configs
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
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/44 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes40,909
source_files_sampled44
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

297GitHub stars
51contributors
103commits, last 12 months
4days since last push
100releases
2bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Could not fetch pypi package 'airflow-chart-dev-env' from its registry

More detail

OpenSSF Scorecard 5.9 / 10
5.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-19 20:49 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
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
10Code-Reviewall changesets reviewed
10Contributorsproject has 16 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 19
RegistryPackageVersion constraintManifest
PyPIdocker>=7.1.0pyproject.toml
PyPIexceptiongroup>=1.3.0pyproject.toml
PyPIfilelock>=3.20.0pyproject.toml
PyPIjinja2>=3.1.6pyproject.toml
PyPIjmespath>=1.0.1pyproject.toml
PyPIjsonschema>=4.25.1pyproject.toml
PyPIkubernetes>=34.1.0pyproject.toml
PyPIpre-commit>=4.3.0pyproject.toml
PyPIpytest>=8.4.2pyproject.toml
PyPIpytest-forked>=1.6.0pyproject.toml
PyPIpytest-pretty>=1.3.0pyproject.toml
PyPIpytest-profiling>=1.8.1pyproject.toml
PyPIpytest-rerunfailures>=16.1pyproject.toml
PyPIpytest-testinfra>=9.0.0pyproject.toml
PyPIpytest-xdist>=3.8.0pyproject.toml
PyPIpyyaml>=6.0.3pyproject.toml
PyPIrequests>=2.32.5pyproject.toml
PyPIsemver>=3.0.4pyproject.toml
PyPIyamllint>=1.37.1pyproject.toml
All dependencies 53

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

RegistryPackageVersionRelation
PyPIdocker7.1.0direct
PyPIexceptiongroup1.3.1direct
PyPIfilelock3.21.0direct
PyPIjinja23.1.6direct
PyPIjmespath1.1.0direct
PyPIjsonschema4.26.0direct
PyPIkubernetes35.0.0direct
PyPIpre-commit4.5.1direct
PyPIpytest9.0.2direct
PyPIpytest-forked1.6.0direct
PyPIpytest-pretty1.3.0direct
PyPIpytest-profiling1.8.1direct
PyPIpytest-rerunfailures16.1direct
PyPIpytest-testinfra10.2.2direct
PyPIpytest-xdist3.8.0direct
PyPIpyyaml6.0.3direct
PyPIrequests2.32.5direct
PyPIsemver3.0.4direct
PyPIyamllint1.38.0direct
PyPIattrs25.4.0indirect
PyPIcertifi2026.1.4indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.4.4indirect
PyPIcolorama0.4.6indirect
PyPIdistlib0.4.0indirect
PyPIdurationpy0.10indirect
PyPIexecnet2.1.2indirect
PyPIgprof2dot2025.4.14indirect
PyPIidentify2.6.16indirect
PyPIidna3.11indirect
PyPIiniconfig2.3.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPImarkdown-it-py4.0.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPInodeenv1.10.0indirect
PyPIoauthlib3.3.1indirect
PyPIpackaging26.0indirect
PyPIpathspec1.0.4indirect
PyPIplatformdirs4.6.0indirect
PyPIpluggy1.6.0indirect
PyPIpy1.11.0indirect
PyPIpygments2.19.2indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpywin32311indirect
PyPIreferencing0.37.0indirect
PyPIrequests-oauthlib2.0.0indirect
PyPIrich14.3.2indirect
PyPIrpds-py0.30.0indirect
PyPIsix1.17.0indirect
PyPIurllib32.6.3indirect
PyPIvirtualenv20.36.1indirect
PyPIwebsocket-client1.9.0indirect
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.15.0 — full methodology · metrics wiki.

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