Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-19 03:55 UTC

jesse-ai / jesse

An advanced trading bot written in Python

PythonMIT★ 8,823 stars⑂ 1,288 forkssince Nov 2018View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

jesse-ai/jesse holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Security (41/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

JesseOrganization · verified domain
384 followers24 public repossince Nov 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIjesse3.6.14,4043898 days ago

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
35.3/36Commit cadence — 51/52 weeks with commits
18/18Commit volume — 521 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year521
human_commit_share0.99
days_since_last_push1
active_weeks_last_year51
How it's scored
16.2/27Ships releases — 41 version tags (no GitHub releases)
36/36Release recency — latest release 8 days ago
27/27Release cadence — a release every ~3.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count41
latest_release_tagv3.6.1
releases_from_tagsyes
days_since_latest_release8
mean_days_between_releases3.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?

72Good · 17% of overall
How it's scored
60/60Stars — 8,823 stars
25/25Forks — 1,288 forks
12.8/15Watchers — 205 watchers
Inputs used
forks1,288
stars8,823
watchers205
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, shields.io
has_pull_request_templateno
How it's scored
48.6/80Monthly downloads — 4,404 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesjesse
dependents—
ecosystemspypi
total_downloads—
monthly_downloads4,404
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?

72Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.8/22.5Commit distribution — top contributor authored 65% of commits
13.5/13.5Contributor breadth — 54 contributors
10/10OpenSSF Scorecard: Contributors — project has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled54
top_contributor_share0.654
How it's scored
41.2/42Issue resolution — 98% of issues closed
19.7/30PR acceptance — 299/456 decided PRs merged
5.8/13Newcomer PR acceptance — 4/9 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/21 approved changesets -- score normalized to 1
Inputs used
merged_prs299
open_issues3
closed_issues168
prs_merged_7d0
prs_decided_7d0
prs_merged_30d12
prs_decided_30d17
issue_closed_ratio0.982
closed_unmerged_prs157
first_time_authors_30d7
first_time_prs_merged_30d4
first_time_prs_decided_30d9
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
18.6/25Owner reach — 384 followers of jesse-ai
22.2/25Track record — 24 public repos, account ~8 yr old
Inputs used
followers384
owner_typeOrganization
is_verifiedyes
owner_loginjesse-ai
public_repos24
account_age_days2,931

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 8 days ago
20/20Version history — 389 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesjesse
ecosystemspypi
any_deprecatedno
min_days_since_publish8

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://jesse.trade
10/10Repository description
10/10Topics — 20 topics
10/10Wiki
Inputs used
topicscryptocurrency, trading-bot, trading-algorithms, trading, crypto, framework, algo-trading, algorithmic-trading, jesse, trading-strategies, python, bot, crypto-bot, bitcoin, trade, crypto-bot-trading, quantitative-finance, quantitative-trading, alpaca, stocks
has_wikiyes
homepagehttps://jesse.trade
docs_sitehttps://jesse.trade
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

41Weak · 16% of overall
How it's scored
0.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 9 out of 9 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.8/7.5Code-Review — Found 3/21 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 7 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
3.5/5SAST — SAST tool detected but not run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 42 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
3.3/35Direct dependencies free of known advisories — 8 affected: pyjwt 2.11.0 (critical 9.1), starkbank-ecdsa 1.1.1 (critical 9.8), cryptography 42.0.8 (high 8.2), +5 more
10/25Indirect dependencies free of known advisories — 1 affected: starlette 0.52.1 (high 7.5)
15.7/40No advisories left outstanding — 8 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,836 days ago
Inputs used
sourceosv
advisories70
affected_packages9
assessed_packages104
unassessed_packages0
affected_by_severitycritical 2, high 5, moderate 2
direct_affected_packages8
Matched the pypi:jesse@3.6.1 runtime dependency closure — what installing the published package pulls in — 104 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.

63Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 76 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.768
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes12,357
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 67 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.67
toolchain_manifests—
dependency_bot_commit_share0.01
How it's scored
0/45Type-checkable code — Python without a type-check config
52.5/55Manageable file sizes — 56/1,247 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes6,925,124
source_files_sampled1,247
oversized_source_files56

Key facts

8,823GitHub stars
54contributors
521commits, last 12 months
1days since last push
41releases
1bus factor
3open 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 ★ / 1,288 ⇿
0Stars
1,288Forks
41Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

2004006008001,0001,2001,4001,288162021-082024-042026-11
Major 1Minor 9Patch 31

Each point covers 5 days.

OpenSSF Scorecard 4.4 / 10
4.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-11-19 03:54 UTC

1Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/21 approved changesets -- score normalized to 1
10Contributorsproject has 7 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 10 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
7SASTSAST tool detected but not run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities42 existing vulnerabilities detected
All dependencies 38

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

RegistryPackageVersionRelation
PyPIaiofiles—indirect
PyPIanyio—indirect
PyPIarrow—indirect
PyPIblinker—indirect
PyPIclick—indirect
PyPIcryptography—indirect
PyPIecdsa—indirect
PyPIeth-account—indirect
PyPIfastapi—indirect
PyPIfnc—indirect
PyPIhttpx—indirect
PyPIjesse-rust1.3.1indirect
PyPIjoblib—indirect
PyPImatplotlib—indirect
PyPImcp1.30.0indirect
PyPImsgpack—indirect
PyPInumpy—indirect
PyPIoptuna—indirect
PyPIpandas—indirect
PyPIpeewee—indirect
PyPIpsycopg2-binary—indirect
PyPIpydash—indirect
PyPIpyjwt—indirect
PyPIpytest—indirect
PyPIpython-dotenv—indirect
PyPIray—indirect
PyPIrequests—indirect
PyPIscikit-learn—indirect
PyPIscipy—indirect
PyPIsimplejson—indirect
PyPIstarkbank-ecdsa—indirect
PyPIstatsmodels—indirect
PyPItabulate—indirect
PyPItimeloop—indirect
PyPIuvicorn—indirect
PyPIwebsocket-client—indirect
PyPIwebsockets—indirect
PyPIwsaccel—indirect
Dependency advisories 9

Installing pypi:jesse@3.6.1 pulls in 104 packages, direct and transitive: 9 carry known advisories, of which 8 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
pyjwt2.11.0directcritical332.15.0
starkbank-ecdsa1.1.1directcritical32.0.1
cryptography42.0.8directhigh1149.0.0
ecdsa0.19.2directhigh2—
mcp1.28.1directhigh42.2.0
msgpack1.1.2directhigh31.2.3
starlette0.52.1indirecthigh101.3.1
pytest6.2.5directmoderate29.0.3
requests2.32.5directmoderate22.33.0

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.