Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-18 06:57 UTC

jebel-quant / jquantstats

Time series and portfolio analytics for quantitative finance.

PythonMIT★ 44 stars⑂ 9 forkssince May 2025View on GitHub ↗

jebel-quant/jquantstats holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (100/100) and lowest on Security (54/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Jebel QuantOrganization
25 followers23 public repossince Jun 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIjquantstats0.9.7-637 days ago

Metrics by category

Vitality

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

97Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recencylast push 0 days ago
36/36Commit cadence52/52 weeks with commits
18/18Commit volume1,062 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,062
human_commit_share
days_since_last_push0
active_weeks_last_year52
How it's scored
27/27Ships releases67 releases published
36/36Release recencylatest release 7 days ago
27/27Release cadencea release every ~6.2 days
2/10OpenSSF Scorecard: Signed-Releases1 out of the last 5 releases have a total of 2 signed artifacts.
Inputs used
releases_count67
latest_release_tagv0.9.7
releases_from_tagsno
days_since_latest_release7
mean_days_between_releases6.2

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

61Moderate · 17% of overall
How it's scored
26.5/60Stars44 stars
7.5/25Forks9 forks
0/15Watchers1 watchers
Inputs used
forks9
stars44
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_services
has_pull_request_templateyes

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.6/22.5Commit distributiontop contributor authored 62% of commits
9.5/13.5Contributor breadth7 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.616
How it's scored
41.2/42Issue resolution98% of issues closed
26.3/30PR acceptance562/640 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/23 approved changesets -- score normalized to 0
Inputs used
merged_prs562
open_issues5
closed_issues248
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.98
closed_unmerged_prs78
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
10.2/25Owner reach25 followers of Jebel-Quant
12.2/25Track record23 public repos, account ~1 yr old
Inputs used
followers25
owner_typeOrganization
is_verified
owner_loginJebel-Quant
public_repos23
account_age_days395
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

100Exceptional · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows11 workflow(s)
24/24Tests present
16/16Linter configruff.toml
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://jebel-quant.github.io/jquantstats/
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsanalytics, dashboard, plotly, polars
has_wikiyes
homepagehttps://jebel-quant.github.io/jquantstats/
docs_sitehttps://jebel-quant.github.io/jquantstats/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

54Moderate · 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
2.5/2.5CI-Tests29 out of 29 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
0/7.5Code-ReviewFound 0/23 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 30 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
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
1.5/7.5Signed-Releases1 out of the last 5 releases have a total of 2 signed artifacts.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities18 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5.4

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.

81Excellent · 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_bytes3,984
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 configruff.toml
11/11Static type checkingsrc/jquantstats/py.typed
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/jquantstats/py.typed
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
27/45Type-checkable codePython with type-check config (src/jquantstats/py.typed)
54.6/55Manageable file sizes1/128 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes66,571
source_files_sampled128
oversized_source_files1

Key facts

44GitHub stars
7contributors
1,062commits, last 12 months
0days since last push
67releases
1bus factor
5open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-18 06:56 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests29 out of 29 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 0/23 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 30 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
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
2Signed-Releases1 out of the last 5 releases have a total of 2 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities18 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
PyPIjinja2>=3.1.0pyproject.toml
PyPInarwhals>=2.0.0pyproject.toml
PyPInumpy>=2.0.0pyproject.toml
PyPIplotly>=6.1.1pyproject.toml
PyPIpolars>=1.42.1pyproject.toml
PyPIscipy>=1.14.1pyproject.toml
All dependencies 128

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

RegistryPackageVersionRelation
PyPIjinja23.1.6direct
PyPInarwhals2.24.0direct
PyPInumpy2.4.6direct
PyPIplotly6.9.0direct
PyPIpolars1.42.1direct
PyPIscipy1.17.1direct
PyPIannotated-doc0.0.4indirect
PyPIannotated-types0.7.0indirect
PyPIanyio4.13.0indirect
PyPIasttokens3.0.1indirect
PyPIbeautifulsoup44.14.3indirect
PyPIcertifi2026.4.22indirect
PyPIcffi2.0.0indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.4.7indirect
PyPIchoreographer1.3.0indirect
PyPIclick8.3.3indirect
PyPIcolorama0.4.6indirect
PyPIcontourpy1.3.3indirect
PyPIcoverage7.14.1indirect
PyPIcurl-cffi0.15.0indirect
PyPIcycler0.12.1indirect
PyPIdecorator5.2.1indirect
PyPIdistlib0.4.0indirect
PyPIdocutils0.22.4indirect
PyPIexecnet2.1.2indirect
PyPIexecuting2.2.1indirect
PyPIfastapi0.139.0indirect
PyPIfilelock3.29.0indirect
PyPIfonttools4.62.1indirect
PyPIglob20.7indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx0.28.1indirect
PyPIhypothesis6.156.6indirect
PyPIidentify2.6.19indirect
PyPIidna3.13indirect
PyPIimportlib-metadata9.0.0indirect
PyPIiniconfig2.3.0indirect
PyPIipython9.15.0indirect
PyPIipython-pygments-lexers1.1.1indirect
PyPIitsdangerous2.2.0indirect
PyPIjedi0.19.2indirect
PyPIjquantstats0.9.7indirect
PyPIjunit-xml1.9indirect
PyPIkaleido1.3.0indirect
PyPIkiwisolver1.5.0indirect
PyPIlogistro2.0.1indirect
PyPIloro1.10.3indirect
PyPImarimo0.23.14indirect
PyPImarkdown3.10.2indirect
PyPImarkdown-it-py4.0.0indirect
PyPImarkupsafe3.0.3indirect
PyPImatplotlib3.10.9indirect
PyPImatplotlib-inline0.2.1indirect
PyPImdurl0.1.2indirect
PyPImsgspec0.21.1indirect
PyPImultitasking0.0.13indirect
PyPImutmut2.5.1indirect
PyPInodeenv1.10.0indirect
PyPIorjson3.11.8indirect
PyPIpackaging26.2indirect
PyPIpandas3.0.3indirect
PyPIparso0.8.7indirect
PyPIpeewee4.0.5indirect
PyPIpexpect4.9.0indirect
PyPIpillow12.2.0indirect
PyPIplatformdirs4.9.6indirect
PyPIpluggy1.6.0indirect
PyPIpolars-runtime-321.42.1indirect
PyPIpony0.7.19indirect
PyPIpre-commit4.6.0indirect
PyPIprompt-toolkit3.0.52indirect
PyPIprotobuf7.34.1indirect
PyPIpsutil7.2.2indirect
PyPIptyprocess0.7.0indirect
PyPIpure-eval0.2.3indirect
PyPIpy-cpuinfo9.0.0indirect
PyPIpyarrow24.0.0indirect
PyPIpycparser3.0indirect
PyPIpydantic2.13.3indirect
PyPIpydantic-core2.46.3indirect
PyPIpygal3.1.3indirect
PyPIpygments2.20.0indirect
PyPIpymdown-extensions10.21.3indirect
PyPIpyparsing3.3.2indirect
PyPIpytest9.1.1indirect
PyPIpytest-benchmark5.2.3indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-html4.2.0indirect
PyPIpytest-metadata3.1.1indirect
PyPIpytest-mock3.15.1indirect
PyPIpytest-timeout2.4.0indirect
PyPIpytest-xdist3.8.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-discovery1.4.0indirect
PyPIpython-dotenv1.2.2indirect
PyPIpython-multipart0.0.32indirect
PyPIpytz2026.2indirect
PyPIpyyaml6.0.3indirect
PyPIpyzmq27.1.0indirect
PyPIquantstats0.0.81indirect
PyPIrequests2.33.1indirect
PyPIrich15.0.0indirect
PyPIseaborn0.13.2indirect
PyPIsimplejson4.1.1indirect
PyPIsix1.17.0indirect
PyPIsortedcontainers2.4.0indirect
PyPIsoupsieve2.8.3indirect
PyPIstack-data0.6.3indirect
PyPIstarlette1.0.0indirect
PyPIsyrupy5.5.3indirect
PyPItabulate0.10.0indirect
PyPItoml0.10.2indirect
PyPItomli2.4.1indirect
PyPItomlkit0.15.0indirect
PyPItraitlets5.14.3indirect
PyPIty0.0.59indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.2indirect
PyPItzdata2026.2indirect
PyPIurllib32.6.3indirect
PyPIuvicorn0.51.0indirect
PyPIvirtualenv21.4.1indirect
PyPIwcwidth0.7.0indirect
PyPIwebsockets16.0indirect
PyPIyfinance1.5.1indirect
PyPIzipp4.1.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.12.0 — full methodology · metrics wiki.

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