Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-12 14:34 UTC

cylc / cylc-flow

Cylc: a general purpose workflow engine with a gift for cycling

Python · ShellGPL-3.0★ 382 stars⑂ 105 forkssince Jun 2011View on GitHub ↗
KindPluginCommand-line toolLibraryTerminal interfacehow this is determined

cylc/cylc-flow holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Vitality (99/100) and lowest on AI Readiness (59/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

55 followers21 public repossince Jun 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIcylc-flow8.7.03,136540 days agocycling-workflowshpcjob-schedulermetaschedulerworkflow-automationworkflow-engineworkflow-managementscheduling

Metrics by category

Vitality

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

99Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
34.6/36Commit cadence — 50/52 weeks with commits
18/18Commit volume — 653 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_year653
human_commit_share0.97
days_since_last_push0
active_weeks_last_year50

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~43.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag8.7.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases43.1
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?

67Good · 17% of overall
How it's scored
41.9/60Stars — 382 stars
16.8/25Forks — 105 forks
6/15Watchers — 13 watchers
Inputs used
forks105
stars382
watchers13
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges9
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
46.6/80Monthly downloads — 3,136 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescylc-flow
dependents—
ecosystemspypi
total_downloads—
monthly_downloads3,136
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?

76Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.3/22.5Commit distribution — top contributor authored 50% of commits
13.5/13.5Contributor breadth — 42 contributors
10/10OpenSSF Scorecard: Contributors — project has 58 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled42
top_contributor_share0.499
How it's scored
33/42Issue resolution — 79% of issues closed
27.6/30PR acceptance — 4,394/4,775 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_prs4,394
open_issues564
closed_issues2,076
prs_merged_7d9
prs_decided_7d11
prs_merged_30d38
prs_decided_30d43
issue_closed_ratio0.786
closed_unmerged_prs381
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
12.6/25Owner reach — 55 followers of cylc
21.8/25Track record — 21 public repos, account ~15 yr old
Inputs used
followers55
owner_typeOrganization
is_verifiedno
owner_logincylc
public_repos21
account_age_days5,611

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 — 54 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescylc-flow
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

89Excellent · 19% of overall
How it's scored
24/24CI workflows — 11 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff], [tool.black], [tool.isort]), tox.ini
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 12 out of 13 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://cylc.github.io
10/10Repository description
10/10Topics — 11 topics
10/10Wiki
Inputs used
topicsworkflow-engine, python, metascheduler, workflow-automation, workflow-management, cycling-workflows, job-scheduler, scheduling, cylc, scheduler, workflow
has_wikiyes
homepagehttps://cylc.github.io
docs_sitehttps://cylc.github.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

72Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.2/2.5CI-Tests — 12 out of 13 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 58 contributing companies or organizations
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 20 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
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_aggregate7.2
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

59Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
26.4/40Legible commit history — 48 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.495
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.black], [tool.isort]), tox.ini
11/11Static type checking — cylc/flow/py.typed, mypy.ini
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configscylc/flow/py.typed, mypy.ini
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (cylc/flow/py.typed, mypy.ini)
54/55Manageable file sizes — 9/479 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes118,776
source_files_sampled479
oversized_source_files9
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — cylc/flow/data_messages.proto
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filescylc/flow/data_messages.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

382GitHub stars
42contributors
653commits, last 12 months
0days since last push
100releases
2bus factor
564open 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:cylc-flow@8.7.0; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 105 ⇿
0Stars
105Forks
97Releases

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.

02040608010012010542011-072019-012026-07
Major 2Minor 16Patch 70

Each point covers 14 days.

OpenSSF Scorecard 7.2 / 10
7.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-10-12 14:33 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
9CI-Tests12 out of 13 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 58 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
PyPIansimarkup>=1.0.0pyproject.toml
PyPIcolorama>=0.4,<1pyproject.toml
PyPIgraphql-core>=3.2,<3.3pyproject.toml
PyPIgraphene>=3.4.0,<3.5pyproject.toml
PyPIjinja2>=3.1pyproject.toml
PyPImetomi-isodatetime>=1!3.2.0,<1!3.3.0pyproject.toml
PyPIpackaging—pyproject.toml
PyPIprotobuf>=5,<8pyproject.toml
PyPIpsutil>=5.6.0pyproject.toml
PyPIpyzmq>=22pyproject.toml
PyPIurwid>=2.2,!=2.6.2,!=2.6.3,<5pyproject.toml
All dependencies 31

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

RegistryPackageVersionRelation
PyPIansimarkup—direct
PyPIcolorama—direct
PyPIgraphene—direct
PyPIgraphql-core—direct
PyPIjinja2—direct
PyPImetomi-isodatetime—direct
PyPIprotobuf—direct
PyPIpsutil—direct
PyPIpyzmq—direct
PyPIurwid—direct
PyPIbandit—indirect
PyPIcoverage—indirect
PyPIflake8—indirect
PyPIflake8-broken-line—indirect
PyPIflake8-bugbear—indirect
PyPIflake8-builtins—indirect
PyPIflake8-comprehensions—indirect
PyPIflake8-debugger—indirect
PyPIflake8-implicit-str-concat—indirect
PyPIflake8-mutable—indirect
PyPImypy—indirect
PyPIpandas—indirect
PyPIpytest—indirect
PyPIpytest-asyncio—indirect
PyPIpytest-cov—indirect
PyPIpytest-mock—indirect
PyPIpytest-xdist—indirect
PyPItestfixtures—indirect
PyPItowncrier—indirect
PyPItypes-jinja2—indirect
PyPItypes-protobuf—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.