Public record
Software health reportschema 0.13.0 · metrics 2.10.0 · 2026-07-18 15:41 UTC

kay-ou / SimTradeLab

SimTradeLab is an open-source backtesting framework inspired by PTrade’s event-driven architecture. It features a lightweight, modular design and full syntax compatibility, enabling seamless strategy development and validation.

PythonAGPL-3.0★ 322 stars⑂ 63 forkssince Jul 2025View on GitHub ↗

kay-ou/SimTradeLab holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (89/100) and lowest on Security (34/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

KayPersonal account
58 followers15 public repossince Feb 2012

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 publishTags
PyPIsimtradelab2.13.2-346 days agoquantitativebacktesttradingstrategyptradefinance

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recencylast push 6 days ago
18/36Commit cadence26/52 weeks with commits
18/18Commit volume179 commits in the last year
10/10OpenSSF Scorecard: Maintained18 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year179
human_commit_share
days_since_last_push6
active_weeks_last_year26

Release discipline

100Exceptional
How it's scored
27/27Ships releases35 releases published
36/36Release recencylatest release 6 days ago
27/27Release cadencea release every ~9.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count35
latest_release_tagv2.13.2
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases9.8
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
40.7/60Stars322 stars
14.9/25Forks63 forks
5.3/15Watchers10 watchers
Inputs used
forks63
stars322
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (AGPL-3.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution100% of issues closed
21.4/30PR acceptance15/21 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs15
open_issues0
closed_issues21
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs6
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
12.7/25Owner reach58 followers of kay-ou
20.8/25Track record15 public repos, account ~14 yr old
Inputs used
followers58
owner_typeUser
is_verified
owner_loginkay-ou
public_repos15
account_age_days5,263
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 6 days ago
20/20Version history34 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessimtradelab
ecosystemspypi
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://github.com/kay-ou/SimTradeDesk
10/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicsbacktesting, backtesting-engine, open-source, ptrade, python3, quantitative-finance, trading-strategy, trading-strategy-simulator, ptrade-compatible
has_wikiyes
homepagehttps://github.com/kay-ou/SimTradeDesk
docs_sitehttps://github.com/kay-ou/SimTradeDesk
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

34At 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-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
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.5Maintained18 commit(s) and 1 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/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): CI-Tests, Signed-Releases. 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.

54Moderate · 4% of overall
How it's scored
45/45Agent instructionssrc/simtradelab/AGENTS.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_filessrc/simtradelab/AGENTS.md
agent_instruction_max_bytes1,609
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePython without a type-check config
54.4/55Manageable file sizes1/87 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes155,971
source_files_sampled87
oversized_source_files1

Key facts

322GitHub stars
1contributors
179commits, last 12 months
6days since last push
35releases
1bus factor
0open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 3.4 / 10
3.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 15:41 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained18 commit(s) and 1 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities16 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
PyPIpandas>=1.5.0pyproject.toml
PyPIpyarrow>=10.0.0pyproject.toml
PyPInumpy>=1.20.0,<2.0pyproject.toml
PyPIcachetools^5.0.0pyproject.toml
PyPIjoblib^1.0.0pyproject.toml
PyPImatplotlib^3.5.0pyproject.toml
PyPItqdm^4.0.0pyproject.toml
PyPIpydantic^2.0.0pyproject.toml
PyPIta-lib*pyproject.toml
PyPIoptuna^3.0.0pyproject.toml
All dependencies 47

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

RegistryPackageVersionRelation
PyPIcachetools5.5.2direct
PyPIjoblib1.5.3direct
PyPImatplotlib3.9.4direct
PyPInumpy1.26.4direct
PyPIoptuna3.6.2direct
PyPIpandas2.3.3direct
PyPIpyarrow21.0.0direct
PyPIpydantic2.13.4direct
PyPIta-lib0.6.8direct
PyPItqdm4.68.1direct
PyPIalembic1.16.5indirect
PyPIannotated-types0.7.0indirect
PyPIbuild1.4.4indirect
PyPIcolorama0.4.6indirect
PyPIcolorlog6.10.1indirect
PyPIcontourpy1.3.0indirect
PyPIcoverage7.10.7indirect
PyPIcycler0.12.1indirect
PyPIexceptiongroup1.3.1indirect
PyPIfonttools4.60.2indirect
PyPIgreenlet3.2.5indirect
PyPIimportlib-metadata8.7.1indirect
PyPIimportlib-resources6.5.2indirect
PyPIiniconfig2.1.0indirect
PyPIkiwisolver1.4.7indirect
PyPImako1.3.12indirect
PyPImarkupsafe3.0.3indirect
PyPIpackaging26.2indirect
PyPIpillow11.3.0indirect
PyPIpluggy1.6.0indirect
PyPIpydantic-core2.46.4indirect
PyPIpygments2.20.0indirect
PyPIpyparsing3.3.2indirect
PyPIpyproject-hooks1.2.0indirect
PyPIpytest8.4.2indirect
PyPIpytest-cov5.0.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpytz2026.2indirect
PyPIpyyaml6.0.3indirect
PyPIruff0.15.21indirect
PyPIsix1.17.0indirect
PyPIsqlalchemy2.0.50indirect
PyPItomli2.4.1indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.2indirect
PyPItzdata2026.2indirect
PyPIzipp3.23.1indirect
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.13.0 — full methodology · metrics wiki.

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