Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 19:43 UTC

ArturSepp / OptimalPortfolios

Production multi-asset portfolio construction and rolling backtesting in Python

PythonMIT★ 98 stars⑂ 43 forkssince Jul 2023View on GitHub ↗

ArturSepp/OptimalPortfolios holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (93/100) and lowest on Community & Adoption (61/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Artur SeppPersonal account
314 followers13 public repossince May 2018LGT Private Banking

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

Package ecosystems

Metrics by category

Vitality

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

93Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
23.5/36Commit cadence — 34/52 weeks with commits
18/18Commit volume — 371 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year371
human_commit_share1
days_since_last_push0
active_weeks_last_year34

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 30 releases published
36/36Release recency — latest release 20 days ago
27/27Release cadence — a release every ~4.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count30
latest_release_tagv7.10.2
releases_from_tagsno
days_since_latest_release20
mean_days_between_releases4.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?

61Moderate · 17% of overall
How it's scored
32.2/60Stars — 98 stars
13.5/25Forks — 43 forks
3.9/15Watchers — 6 watchers
Inputs used
forks43
stars98
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, readthedocs.org, shields.io
has_pull_request_templateyes
How it's scored
43.8/80Monthly downloads — 1,910 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesoptimalportfolios
dependents—
ecosystemspypi
total_downloads—
monthly_downloads1,910
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.8/22.5Commit distribution — top contributor authored 92% of commits
5.4/13.5Contributor breadth — 4 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.921
How it's scored
42/42Issue resolution — 100% of issues closed
26/30PR acceptance — 71/82 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/22 approved changesets -- score normalized to 0
Inputs used
merged_prs71
open_issues0
closed_issues36
prs_merged_7d3
prs_decided_7d3
prs_merged_30d33
prs_decided_30d35
issue_closed_ratio1
closed_unmerged_prs11
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
18/25Owner reach — 314 followers of ArturSepp
20.3/25Track record — 13 public repos, account ~8 yr old
Inputs used
followers314
owner_typeUser
is_verified—
owner_loginArturSepp
public_repos13
account_age_days3,064
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 4 days ago
20/20Version history — 123 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesoptimalportfolios
ecosystemspypi
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows — 10 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 7 out of 7 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

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://optimalportfolios.readthedocs.io
10/10Repository description
10/10Topics — 10 topics
10/10Wiki
Inputs used
topicsbacktesting, backtesting-trading-strategies, cvxpy, optimal-portfolio, portfolio-optimization, asset-allocation, covariance-estimation, factor-models, python, quantitative-finance
has_wikiyes
homepagehttps://optimalportfolios.readthedocs.io
docs_sitehttps://optimalportfolios.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

69Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 7 out of 7 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 0/22 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
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
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.1
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
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages43
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:optimalportfolios@7.22.1 runtime dependency closure — what installing the published package pulls in — 43 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.

77Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md, papers/AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://optimalportfolios.readthedocs.io/llms.txt)
35.7/40Legible commit history — 67 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://optimalportfolios.readthedocs.io/llms.txt
legible_history_share0.67
agent_instruction_filesAGENTS.md, CLAUDE.md, papers/AGENTS.md
agent_instruction_max_bytes43,485
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 41 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.41
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
54.7/55Manageable file sizes — 2/369 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes83,761
source_files_sampled369
oversized_source_files2
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 — examples, 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

98GitHub stars
4contributors
371commits, last 12 months
0days since last push
30releases
1bus factor
0open 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 ★ / 43 ⇿
0Stars
43Forks
30Releases

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.

010203040504222023-082025-032026-10
Major 1Minor 20Patch 9

Each point covers 3 days.

OpenSSF Scorecard 6.1 / 10
6.1aggregate

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-21 19:43 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests7 out of 7 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/22 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
PyPInumpy>=2.0pyproject.toml
PyPIscipy>=1.12.0pyproject.toml
PyPIpandas>=2.2.0pyproject.toml
PyPImatplotlib>=3.8.0pyproject.toml
PyPIPillow>=13.0.0pyproject.toml
PyPIseaborn>=0.13.0pyproject.toml
PyPIopenpyxl>=3.1.0pyproject.toml
PyPIPyYAML>=6.0pyproject.toml
PyPIcvxpy>=1.5.2pyproject.toml
PyPIscs>=3.2.4.post3,!=3.3.0pyproject.toml
PyPIqis>=5.38.1pyproject.toml
All dependencies 117

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

RegistryPackageVersionRelation
PyPIcvxpy1.9.2direct
PyPImatplotlib3.11.1direct
PyPInumpy2.4.6direct
PyPInumpy2.5.2direct
PyPIopenpyxl3.1.5direct
PyPIpandas3.0.5direct
PyPIpillow13.0.0direct
PyPIpyyaml6.0.3direct
PyPIqis5.38.1direct
PyPIscipy1.17.1direct
PyPIscipy1.18.0direct
PyPIscs3.2.11direct
PyPIseaborn0.13.2direct
PyPIaccessible-pygments0.0.5indirect
PyPIalabaster1.0.0indirect
PyPIattrs26.1.0indirect
PyPIbabel2.18.0indirect
PyPIbeautifulsoup44.15.0indirect
PyPIboolean-py5.0indirect
PyPIcachecontrol0.14.4indirect
PyPIcertifi2026.10.19indirect
PyPIcffi2.1.1indirect
PyPIcharset-normalizer3.5.0indirect
PyPIclarabel0.11.1indirect
PyPIclick8.4.2indirect
PyPIcolorama0.4.6indirect
PyPIcontourpy1.3.3indirect
PyPIcoverage7.15.4indirect
PyPIcurl-cffi0.16.0indirect
PyPIcycler0.12.1indirect
PyPIcyclonedx-python-lib11.11.2indirect
PyPIdefusedxml0.7.1indirect
PyPIdeptry0.25.1indirect
PyPIdocutils0.22.4indirect
PyPIet-xmlfile2.0.0indirect
PyPIfilelock3.32.2indirect
PyPIfonttools4.63.0indirect
PyPIfuro2025.12.19indirect
PyPIhighspy1.15.1indirect
PyPIhtml5lib1.1indirect
PyPIidna3.18indirect
PyPIimagesize2.0.0indirect
PyPIiniconfig2.3.0indirect
PyPIinterrogate1.7.0indirect
PyPIjinja23.1.6indirect
PyPIjoblib1.5.3indirect
PyPIkiwisolver1.5.0indirect
PyPIlicense-expression30.4.4indirect
PyPIllvmlite0.49.0indirect
PyPIlxml6.1.1indirect
PyPImarkdown3.10.3indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdit-py-plugins0.6.1indirect
PyPImdurl0.1.2indirect
PyPImosek11.2.3indirect
PyPImsgpack1.2.1indirect
PyPImultitasking0.0.13indirect
PyPImyst-parser5.1.0indirect
PyPInumba0.67.0indirect
PyPIoptimalportfolios8.0.0rc2indirect
PyPIosqp1.1.3indirect
PyPIpackageurl-python0.17.6indirect
PyPIpackaging26.3indirect
PyPIpatsy1.0.2indirect
PyPIpeewee4.3.0indirect
PyPIpip26.2.1indirect
PyPIpip-api0.0.34indirect
PyPIpip-audit2.10.1indirect
PyPIpip-requirements-parser32.0.1indirect
PyPIplatformdirs4.11.2indirect
PyPIpluggy1.6.0indirect
PyPIprotobuf7.35.1indirect
PyPIpy1.11.0indirect
PyPIpy-serializable2.1.0indirect
PyPIpybloqs1.4.3indirect
PyPIpycparser3.0indirect
PyPIpygments2.20.0indirect
PyPIpyparsing3.3.2indirect
PyPIpytest9.1.1indirect
PyPIpytest-cov7.1.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpytz2026.3.post1indirect
PyPIqdldl0.1.9.post1indirect
PyPIquadprog0.1.13indirect
PyPIrequests2.34.2indirect
PyPIrequirements-parser0.13.1indirect
PyPIrich15.0.0indirect
PyPIroman-numerals4.1.0indirect
PyPIruff0.16.9indirect
PyPIsetuptools84.0.0indirect
PyPIsix1.17.0indirect
PyPIsnowballstemmer3.1.1indirect
PyPIsortedcontainers2.4.0indirect
PyPIsoupsieve2.9.2indirect
PyPIsparsediffpy0.3.0indirect
PyPIsphinx9.0.4indirect
PyPIsphinx9.1.0indirect
PyPIsphinx-basic-ng1.0.0b2indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-mermaid2.1.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPIstatsmodels0.14.6indirect
PyPItabulate0.10.0indirect
PyPItomli2.4.1indirect
PyPItomli-w1.2.0indirect
PyPItyping-extensions4.16.0indirect
PyPItzdata2026.3indirect
PyPIurllib32.8.0indirect
PyPIuv0.12.23indirect
PyPIwebencodings0.5.1indirect
PyPIwebsockets17.0.1indirect
PyPIyfinance1.5.2indirect
Dependency advisories 0

Installing pypi:optimalportfolios@7.22.1 pulls in 43 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 statistics — PyPI.