Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 22:31 UTC

OpenSourceAP / CrossSection

Code to accompany our paper Chen and Zimmermann (2020), "Open source cross-sectional asset pricing"

Python · HTML · StataGPL-2.0★ 1,027 stars⑂ 282 forkssince May 2020View on GitHub ↗

OpenSourceAP/CrossSection holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on Community & Adoption (65/100) and lowest on AI Readiness (26/100). It was last updated 295 days ago. A single contributor accounts for most of its recent work.

45
overall / 100
Weak

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.

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

Ownership

OpenSourceAPPersonal account
141 followers2 public repossince May 2020

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

Metrics by category

Vitality

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

43Weak · 21% of overall
How it's scored
3.6/36Push recencylast push 295 days ago
6.9/36Commit cadence10/52 weeks with commits
18/18Commit volume543 commits in the last year
2/10OpenSSF Scorecard: Maintained0 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year543
human_commit_share1
days_since_last_push295
active_weeks_last_year10
How it's scored
27/27Ships releases10 releases published
16.2/36Release recencylatest release 295 days ago
12.6/27Release cadencea release every ~213.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count10
latest_release_tagv2.0.0
releases_from_tagsno
days_since_latest_release295
mean_days_between_releases213.2
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?

65Good · 17% of overall
How it's scored
48.8/60Stars1,027 stars
20.4/25Forks282 forks
8.6/15Watchers36 watchers
Inputs used
forks282
stars1,027
watchers36
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

50Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.4/22.5Commit distributiontop contributor authored 80% of commits
12.2/13.5Contributor breadth9 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.803
How it's scored
38/42Issue resolution90% of issues closed
26.9/30PR acceptance53/59 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/2 approved changesets -- score normalized to 0
Inputs used
merged_prs53
open_issues14
closed_issues134
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.905
closed_unmerged_prs6
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
15.5/25Owner reach141 followers of OpenSourceAP
15.5/25Track record2 public repos, account ~6 yr old
Inputs used
followers141
owner_typeUser
is_verified
owner_loginOpenSourceAP
public_repos2
account_age_days2,288
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

54Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://papers.ssrn.com/sol3/papers.cfm?abstract_id=3604626
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsasset-pricing, finance, quantitative-finance, reproducible-research, stocks
has_wikiyes
homepagehttps://papers.ssrn.com/sol3/papers.cfm?abstract_id=3604626
docs_sitehttps://papers.ssrn.com/sol3/papers.cfm?abstract_id=3604626
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

27At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/2 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
1.5/7.5Maintained0 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 2
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.7
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

26At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
9.6/40Legible commit history18 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.18
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/349 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes58,679
source_files_sampled349
oversized_source_files0

Key facts

1,027GitHub stars
9contributors
543commits, last 12 months
295days since last push
10releases
1bus factor
14open issues
package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 282 ⇿
0Stars
282Forks
10Releases

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.

050100150200250300275292020-062023-072026-08
Major 2Minor 5Patch 3

Each point covers 6 days.

OpenSSF Scorecard 2.7 / 10
2.7aggregate

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-08-13 22:31 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/2 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained0 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 35

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

RegistryPackageVersionRelation
PyPI-gwtmeanindirect
PyPIasregindirect
PyPIasrolindirect
PyPIastileindirect
PyPIdtaleindirect
PyPIegenmiscindirect
PyPIegenmoreindirect
PyPIfastxtileindirect
PyPIfilelistindirect
PyPIfreduseindirect
PyPIfsindirect
PyPIfsumindirect
PyPIftoolsindirect
PyPIgtoolsindirect
PyPImdescindirect
PyPImoremataindirect
PyPInumpyindirect
PyPIopenassetpricingindirect
PyPIopenpyxlindirect
PyPIpandasindirect
PyPIpolarsindirect
PyPIpolars-olsindirect
PyPIpsycopg2-binaryindirect
PyPIpyarrowindirect
PyPIpyreadstatindirect
PyPIpython-dotenvindirect
PyPIpyyamlindirect
PyPIrelrankindirect
PyPIrequestsindirect
PyPIrscriptindirect
PyPIsicffindirect
PyPIsqlalchemyindirect
PyPIstatsmodelsindirect
PyPItscollapindirect
PyPIwinsor2indirect
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.31.0 — full methodology · metrics wiki.

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