Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 07:41 UTC

BrianPugh / cyclopts

Intuitive, easy CLIs based on python type hints.

PythonApache-2.0★ 1,250 stars⑂ 56 forkssince Nov 2023View on GitHub ↗
KindCommand-line toolPluginLibraryhow this is determined

BrianPugh/cyclopts holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Vitality (99/100) and lowest on Security (57/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Brian PughPersonal account
163 followers151 public repossince Sep 2015

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 publish
PyPIcyclopts4.25.2-1610 days ago

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 — 749 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year749
human_commit_share1
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 ~3.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv4.25.2
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases3.9
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?

69Good · 17% of overall
How it's scored
50.2/60Stars — 1,250 stars
14.5/25Forks — 56 forks
3.3/15Watchers — 5 watchers
Inputs used
forks56
stars1,250
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, readthedocs.org, shields.io
has_pull_request_templateno

Sustainability & Governance

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

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.2/22.5Commit distribution — top contributor authored 95% of commits
13.5/13.5Contributor breadth — 35 contributors
10/10OpenSSF Scorecard: Contributors — project has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled35
top_contributor_share0.948
How it's scored
39.6/42Issue resolution — 94% of issues closed
25.5/30PR acceptance — 520/611 decided PRs merged
13/13Newcomer PR acceptance — 8/8 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/11 approved changesets -- score normalized to 0
Inputs used
merged_prs520
open_issues19
closed_issues307
prs_merged_7d16
prs_decided_7d21
prs_merged_30d35
prs_decided_30d44
issue_closed_ratio0.942
closed_unmerged_prs91
first_time_authors_30d7
first_time_prs_merged_30d8
first_time_prs_decided_30d8
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
15.9/25Owner reach — 163 followers of BrianPugh
25/25Track record — 151 public repos, account ~10 yr old
Inputs used
followers163
owner_typeUser
is_verified—
owner_loginBrianPugh
public_repos151
account_age_days4,010
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 — 161 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescyclopts
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 11 out of 11 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/10Topics — 5 topics
0/10Wiki
Inputs used
topicsargument-parser, python, shell, typehints, cli
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?

57Moderate · 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 — 11 out of 11 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/11 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 10 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 24 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
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 25 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.6
Excluded from scoring (no data or not applicable): 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
advisories33
affected_packages2
assessed_packages103
unassessed_packages1
affected_by_severitycritical 1, high 1
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 103 resolved dependencies against OSV. 1 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.

78Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.pydantic.dev/llms.txt)
40/40Legible commit history — 94 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.pydantic.dev/llms.txt
legible_history_share0.94
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — cyclopts/py.typed
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 66 of the last 100 commits agent-authored or agent-credited
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
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configscyclopts/py.typed
agent_commit_share0.66
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (cyclopts/py.typed)
54/55Manageable file sizes — 4/227 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes160,822
source_files_sampled227
oversized_source_files4
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — cookbook
Inputs used
example_dirscookbook
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

1,250GitHub stars
35contributors
749commits, last 12 months
0days since last push
100releases
1bus factor
19open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'cyclopts' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • deps.dev does not index pypi:cyclopts@4.25.2; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 56 ⇿
0Stars
56Forks
98Releases

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.

01020304050605622023-122025-042026-09
Major 1Minor 40Patch 46

Each point covers 3 days.

OpenSSF Scorecard 4.6 / 10
4.6aggregate

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

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests11 out of 11 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/11 approved changesets -- score normalized to 0
10Contributorsproject has 10 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 24 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities25 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
PyPIattrs>=23.1.0pyproject.toml
PyPIrich>=13.6.0pyproject.toml
PyPIdocstring-parser>=0.15,<4.0pyproject.toml
PyPIrich-rst>=1.3.1,<3.0.0pyproject.toml
PyPItyping-extensions>=4.8.0pyproject.toml
PyPItomli>=2.0.0pyproject.toml
All dependencies 104

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

RegistryPackageVersionRelation
PyPIattrs26.1.0direct
PyPIdocstring-parser0.18.0direct
PyPIrich15.0.0direct
PyPIrich-rst2.0.1direct
PyPItomli2.4.1direct
PyPItyping-extensions4.15.0direct
PyPIalabaster1.0.0indirect
PyPIannotated-types0.7.0indirect
PyPIasttokens3.0.1indirect
PyPIbabel2.18.0indirect
PyPIcertifi2026.4.22indirect
PyPIcffi2.0.0indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.4.7indirect
PyPIclick8.4.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.14.0indirect
PyPIcyclopts—indirect
PyPIdecorator5.3.1indirect
PyPIdistlib0.4.0indirect
PyPIdocutils0.21.2indirect
PyPIexceptiongroup1.3.1indirect
PyPIexecuting2.2.1indirect
PyPIfilelock3.29.0indirect
PyPIghp-import2.1.0indirect
PyPIgitdb4.0.12indirect
PyPIgitpython3.1.50indirect
PyPIidentify2.6.19indirect
PyPIidna3.15indirect
PyPIimagesize2.0.0indirect
PyPIiniconfig2.3.0indirect
PyPIipdb0.13.13indirect
PyPIipython8.39.0indirect
PyPIipython9.13.0indirect
PyPIipython-pygments-lexers1.1.1indirect
PyPIjedi0.20.0indirect
PyPIjinja23.1.6indirect
PyPIline-profiler5.0.2indirect
PyPIlinkify-it-py2.1.0indirect
PyPImarkdown3.10.2indirect
PyPImarkdown-it-py3.0.0indirect
PyPImarkupsafe3.0.3indirect
PyPImatplotlib-inline0.2.2indirect
PyPImdit-py-plugins0.6.1indirect
PyPImdurl0.1.2indirect
PyPImergedeep1.3.4indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImyst-parser4.0.1indirect
PyPInodeenv1.10.0indirect
PyPIoutcome1.3.0.post0indirect
PyPIpackaging26.2indirect
PyPIparso0.8.7indirect
PyPIpathspec1.1.1indirect
PyPIpexpect4.9.0indirect
PyPIplatformdirs4.9.6indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.6.0indirect
PyPIprompt-toolkit3.0.52indirect
PyPIpsutil7.2.2indirect
PyPIptyprocess0.7.0indirect
PyPIpure-eval0.2.3indirect
PyPIpycparser3.0indirect
PyPIpydantic2.13.4indirect
PyPIpydantic-core2.46.4indirect
PyPIpygments2.20.0indirect
PyPIpymdown-extensions10.21.3indirect
PyPIpytest9.0.3indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-mock3.15.1indirect
PyPIpytest-timeout2.4.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-discovery1.3.1indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIrequests2.34.2indirect
PyPIsix1.17.0indirect
PyPIsmmap5.0.3indirect
PyPIsniffio1.3.1indirect
PyPIsnowballstemmer3.0.1indirect
PyPIsortedcontainers2.4.0indirect
PyPIsphinx8.1.3indirect
PyPIsphinx-autodoc-typehints3.0.1indirect
PyPIsphinx-copybutton0.5.2indirect
PyPIsphinx-rtd-dark-mode1.3.0indirect
PyPIsphinx-rtd-theme3.1.0indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jquery4.1indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPIstack-data0.6.3indirect
PyPIsyrupy5.2.0indirect
PyPItoml0.10.2indirect
PyPItraitlets5.15.0indirect
PyPItrio0.33.0indirect
PyPItyping-inspection0.4.2indirect
PyPIuc-micro-py2.0.0indirect
PyPIurllib32.7.0indirect
PyPIvirtualenv21.3.3indirect
PyPIwatchdog6.0.0indirect
PyPIwcwidth0.7.0indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
gitpython3.1.50indirectcritical293.1.59
pymdown-extensions10.21.3indirecthigh411.0.1

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.