Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 14:24 UTC

LSSTDESC / CCL

DESC Core Cosmology Library: cosmology routines with validated numerical accuracy

C · PythonBSD-3-Clause★ 160 stars⑂ 85 forkssince Apr 2016View on GitHub ↗

LSSTDESC/CCL holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (88/100) and lowest on AI Readiness (60/100). It was last updated 47 days ago. 6 contributors account 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

239 followers486 public repossince Nov 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIpyccl3.3.65,0604147 days agocosmologyastrophysicsphysicssciencelsst

Metrics by category

Vitality

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

73Good · 21% of overall
How it's scored
18/36Push recencylast push 47 days ago
13.8/36Commit cadence20/52 weeks with commits
18/18Commit volume125 commits in the last year
10/10OpenSSF Scorecard: Maintained13 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year125
human_commit_share1
days_since_last_push47
active_weeks_last_year20
How it's scored
27/27Ships releases39 releases published
36/36Release recencylatest release 47 days ago
19.8/27Release cadencea release every ~61.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count39
latest_release_tagv3.3.6
releases_from_tagsno
days_since_latest_release47
mean_days_between_releases61.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?

66Good · 17% of overall
How it's scored
35.7/60Stars160 stars
16/25Forks85 forks
13.1/15Watchers230 watchers
Inputs used
forks85
stars160
watchers230
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (BSD-3-Clause)
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_servicescoveralls.io, github.com, readthedocs.org, shields.io
has_pull_request_templateno
How it's scored
49.4/80Monthly downloads5,060 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespyccl
dependents
ecosystemspypi
total_downloads
monthly_downloads5,060
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?

88Excellent · 23% of overall
How it's scored
48.6/54Bus factor6 contributor(s) cover half of all commits
18.6/22.5Commit distributiontop contributor authored 17% of commits
13.5/13.5Contributor breadth63 contributors
10/10OpenSSF Scorecard: Contributorsproject has 41 contributing companies or organizations
Inputs used
bus_factor6
contributors_sampled63
top_contributor_share0.172
How it's scored
37.1/42Issue resolution88% of issues closed
25/30PR acceptance556/667 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_prs556
open_issues73
closed_issues553
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.883
closed_unmerged_prs111
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
30/30Ownership backingorganization-owned
0/20Verified domain
17.1/25Owner reach239 followers of LSSTDESC
25/25Track record486 public repos, account ~13 yr old
Inputs used
followers239
owner_typeOrganization
is_verifiedno
owner_loginLSSTDESC
public_repos486
account_age_days5,059

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 47 days ago
20/20Version history41 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespyccl
ecosystemspypi
any_deprecatedno
min_days_since_publish47

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.flake8
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests8 out of 8 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://ccl.readthedocs.io/en/latest/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://ccl.readthedocs.io/en/latest/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

66Good · 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-Tests8 out of 8 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 41 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
7.5/7.5Maintained13 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages4
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:pyccl@3.3.6 runtime dependency closure — what installing the published package pulls in — 4 packages. 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
18.1/40Legible commit history34 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.34
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile, benchmarks/data/codes/CosmicEmuMTII/P_cb/makefile, benchmarks/data/codes/CosmicEmuMTII/P_tot/makefile, benchmarks/data/codes/CosmicEmuMTIV/P_cb/makefile, benchmarks/data/codes/CosmicEmuMTIV/P_tot/makefile, benchmarks/data/codes/cl_corr_bm/Makefile, doc/0000-ccl_note/Makefile, doc/ccl_paper/Makefile, readthedocs/Makefile
22/22Automated tests
11/11Lint / format config.flake8
11/11Static type checkingC (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
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
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile, benchmarks/data/codes/CosmicEmuMTII/P_cb/makefile, benchmarks/data/codes/CosmicEmuMTII/P_tot/makefile, benchmarks/data/codes/CosmicEmuMTIV/P_cb/makefile, benchmarks/data/codes/CosmicEmuMTIV/P_tot/makefile, benchmarks/data/codes/cl_corr_bm/Makefile, doc/0000-ccl_note/Makefile, doc/ccl_paper/Makefile, readthedocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeC (statically typed)
54/55Manageable file sizes5/277 source files over 60KB
Inputs used
primary_languageC
largest_source_bytes1,428,745
source_files_sampled277
oversized_source_files5
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, notebooks
Inputs used
example_dirsexamples, notebooks
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

160GitHub stars
63contributors
125commits, last 12 months
47days since last push
39releases
6bus factor
73open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 85 ⇿
0Stars
85Forks
38Releases

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.

0204060801008332017-072022-012026-08
Major 3Minor 8Patch 17

Each point covers 9 days.

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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-13 14:23 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-Tests8 out of 8 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 41 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained13 commit(s) and 3 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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
PyPInumpypyproject.toml
PyPIpackagingpyproject.toml
PyPIscipypyproject.toml
PyPIpyyamlpyproject.toml
All dependencies 230

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

RegistryPackageVersionRelation
PyPInumpydirect
PyPIpackagingdirect
PyPIpyyamldirect
PyPIscipydirect
PyPI10indirect
PyPI1007indirect
PyPI101indirect
PyPI1027indirect
PyPI1047indirect
PyPI106indirect
PyPI1067indirect
PyPI1087indirect
PyPI11indirect
PyPI1107indirect
PyPI111indirect
PyPI1127indirect
PyPI1147indirect
PyPI116indirect
PyPI1167indirect
PyPI1187indirect
PyPI12indirect
PyPI1207indirect
PyPI121indirect
PyPI1227indirect
PyPI1247indirect
PyPI1267indirect
PyPI127indirect
PyPI1287indirect
PyPI13indirect
PyPI1307indirect
PyPI1327indirect
PyPI133indirect
PyPI1347indirect
PyPI1367indirect
PyPI1387indirect
PyPI139indirect
PyPI14indirect
PyPI1407indirect
PyPI1427indirect
PyPI1447indirect
PyPI145indirect
PyPI1467indirect
PyPI1487indirect
PyPI15indirect
PyPI1507indirect
PyPI152indirect
PyPI1527indirect
PyPI1547indirect
PyPI1567indirect
PyPI1587indirect
PyPI159indirect
PyPI16indirect
PyPI1607indirect
PyPI1627indirect
PyPI1647indirect
PyPI166indirect
PyPI1667indirect
PyPI1687indirect
PyPI17indirect
PyPI1707indirect
PyPI1727indirect
PyPI174indirect
PyPI1747indirect
PyPI1767indirect
PyPI1787indirect
PyPI18indirect
PyPI1807indirect
PyPI182indirect
PyPI1827indirect
PyPI1847indirect
PyPI1867indirect
PyPI1887indirect
PyPI19indirect
PyPI1907indirect
PyPI191indirect
PyPI1927indirect
PyPI1947indirect
PyPI1967indirect
PyPI1987indirect
PyPI2indirect
PyPI20indirect
PyPI200indirect
PyPI2007indirect
PyPI2027indirect
PyPI2047indirect
PyPI2067indirect
PyPI2087indirect
PyPI21indirect
PyPI210indirect
PyPI2107indirect
PyPI2127indirect
PyPI2147indirect
PyPI2167indirect
PyPI2187indirect
PyPI22indirect
PyPI220indirect
PyPI2207indirect
PyPI2227indirect
PyPI2247indirect
PyPI2267indirect
PyPI2287indirect
PyPI23indirect
PyPI2307indirect
PyPI231indirect
PyPI2327indirect
PyPI2347indirect
PyPI2367indirect
PyPI2387indirect
PyPI24indirect
PyPI2407indirect
PyPI242indirect
PyPI2427indirect
PyPI2447indirect
PyPI2467indirect
PyPI2487indirect
PyPI25indirect
PyPI2507indirect
PyPI2527indirect
PyPI254indirect
PyPI2547indirect
PyPI2567indirect
PyPI2587indirect
PyPI26indirect
PyPI2607indirect
PyPI2627indirect
PyPI2647indirect
PyPI266indirect
PyPI2667indirect
PyPI2687indirect
PyPI27indirect
PyPI2707indirect
PyPI2727indirect
PyPI2747indirect
PyPI2767indirect
PyPI2787indirect
PyPI279indirect
PyPI28indirect
PyPI2807indirect
PyPI2827indirect
PyPI2847indirect
PyPI2867indirect
PyPI2887indirect
PyPI29indirect
PyPI2907indirect
PyPI292indirect
PyPI2927indirect
PyPI2947indirect
PyPI2967indirect
PyPI2987indirect
PyPI3indirect
PyPI30indirect
PyPI306indirect
PyPI31indirect
PyPI32indirect
PyPI321indirect
PyPI33indirect
PyPI337indirect
PyPI34indirect
PyPI35indirect
PyPI353indirect
PyPI36indirect
PyPI37indirect
PyPI370indirect
PyPI38indirect
PyPI388indirect
PyPI39indirect
PyPI4indirect
PyPI40indirect
PyPI407indirect
PyPI42indirect
PyPI427indirect
PyPI44indirect
PyPI447indirect
PyPI46indirect
PyPI467indirect
PyPI48indirect
PyPI487indirect
PyPI5indirect
PyPI50indirect
PyPI507indirect
PyPI52indirect
PyPI527indirect
PyPI54indirect
PyPI547indirect
PyPI56indirect
PyPI567indirect
PyPI58indirect
PyPI587indirect
PyPI6indirect
PyPI60indirect
PyPI607indirect
PyPI627indirect
PyPI63indirect
PyPI647indirect
PyPI66indirect
PyPI667indirect
PyPI687indirect
PyPI69indirect
PyPI7indirect
PyPI707indirect
PyPI72indirect
PyPI727indirect
PyPI747indirect
PyPI75indirect
PyPI767indirect
PyPI78indirect
PyPI787indirect
PyPI8indirect
PyPI807indirect
PyPI81indirect
PyPI827indirect
PyPI847indirect
PyPI85indirect
PyPI867indirect
PyPI887indirect
PyPI89indirect
PyPI9indirect
PyPI907indirect
PyPI927indirect
PyPI93indirect
PyPI947indirect
PyPI967indirect
PyPI97indirect
PyPI987indirect
PyPIdocutilsindirect
PyPIsetuptoolsindirect
PyPIsetuptools-scmindirect
PyPIsphinxindirect
PyPIsphinx-mdincludeindirect
PyPIsphinx-rtd-themeindirect
Dependency advisories 0

Installing pypi:pyccl@3.3.6 pulls in 4 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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