Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 23:51 UTC

jesse-ai / jesse

An advanced crypto trading bot written in Python

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

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

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

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

Ownership

JesseOrganization · verified domain
369 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.1.5-3701 day 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 recencylast push 1 days ago
35.3/36Commit cadence51/52 weeks with commits
18/18Commit volume441 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year441
human_commit_share0.99
days_since_last_push1
active_weeks_last_year51
How it's scored
16.2/27Ships releases22 version tags (no GitHub releases)
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~4.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count22
latest_release_tagv3.1.5
releases_from_tagsyes
days_since_latest_release1
mean_days_between_releases4.4
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?

76Good · 17% of overall
How it's scored
60/60Stars8,518 stars
25/25Forks1,231 forks
12.9/15Watchers209 watchers
Inputs used
forks1,231
stars8,518
watchers209
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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

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 factor1 contributor(s) cover half of all commits
8/22.5Commit distributiontop contributor authored 64% of commits
13.5/13.5Contributor breadth50 contributors
10/10OpenSSF Scorecard: Contributorsproject has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled50
top_contributor_share0.644
How it's scored
40.2/42Issue resolution96% of issues closed
19.8/30PR acceptance282/428 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/28 approved changesets -- score normalized to 0
Inputs used
merged_prs282
open_issues7
closed_issues154
prs_merged_7d1
prs_decided_7d1
prs_merged_30d4
prs_decided_30d5
issue_closed_ratio0.957
closed_unmerged_prs146
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
30/30Ownership backingorganization-owned
20/20Verified domain
18.5/25Owner reach369 followers of jesse-ai
22.2/25Track record24 public repos, account ~7 yr old
Inputs used
followers369
owner_typeOrganization
is_verifiedyes
owner_loginjesse-ai
public_repos24
account_age_days2,867

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

59Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
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 sitehttps://jesse.trade
10/10Repository description
10/10Topics18 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
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?

38Weak · 16% of overall
How it's scored
0.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 1 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/28 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 7 contributing companies or organizations
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 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
3.5/5SASTSAST tool detected but not run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities25 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
3.4/35Direct dependencies free of known advisories8 affected: starkbank-ecdsa 1.1.1 (critical 9.8), click 8.0.4 (high 7.2), cryptography 42.0.8 (high 8.2), +5 more
10/25Indirect dependencies free of known advisories1 affected: starlette 0.52.1 (high 7.5)
16/40No advisories left outstanding8 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,772 days ago
Inputs used
sourceosv
advisories45
affected_packages9
assessed_packages111
unassessed_packages0
affected_by_severitycritical 1, high 6, moderate 2
direct_affected_packages8
Matched the pypi:jesse@3.1.5 runtime dependency closure — what installing the published package pulls in — 111 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.

54Moderate · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
14/40Legible commit history26 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.263
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes11,066
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentDockerfile
10/10Demonstrated agent practice11 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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.11
toolchain_manifests
dependency_bot_commit_share0.01
How it's scored
0/45Type-checkable codePython without a type-check config
52.5/55Manageable file sizes53/1,153 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes6,915,612
source_files_sampled1,153
oversized_source_files53

Key facts

8,518GitHub stars
50contributors
441commits, last 12 months
1days since last push
22releases
1bus factor
7open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'jesse' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced

More detail

Star and fork history 0 ★ / 1,231 ⇿
0Stars
1,231Forks
21Releases

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.

02505007501,0001,2501,231132021-052024-012026-09
Major 1Minor 4Patch 16

Each point covers 5 days.

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-09-15 23:50 UTC

1Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 1 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/28 approved changesets -- score normalized to 0
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 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
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
0Vulnerabilities25 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
PyPIaiofilesindirect
PyPIaioredisindirect
PyPIarrowindirect
PyPIblinkerindirect
PyPIclickindirect
PyPIcryptographyindirect
PyPIecdsaindirect
PyPIeth-accountindirect
PyPIfastapiindirect
PyPIfncindirect
PyPIjesse-rust1.2.0indirect
PyPIjoblibindirect
PyPImatplotlibindirect
PyPImcp1.28.1indirect
PyPImsgpackindirect
PyPInumpyindirect
PyPIoptunaindirect
PyPIpandasindirect
PyPIpeeweeindirect
PyPIpsycopg2-binaryindirect
PyPIpydashindirect
PyPIpyjwtindirect
PyPIpytestindirect
PyPIpython-dotenvindirect
PyPIrayindirect
PyPIredisindirect
PyPIrequestsindirect
PyPIscikit-learnindirect
PyPIscipyindirect
PyPIsimplejsonindirect
PyPIstarkbank-ecdsaindirect
PyPIstatsmodelsindirect
PyPItabulateindirect
PyPItimeloopindirect
PyPIuvicornindirect
PyPIwebsocket-clientindirect
PyPIwebsocketsindirect
PyPIwsaccelindirect
Dependency advisories 9

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

PackageVersionRelationSeverityAdvisoriesFixed in
starkbank-ecdsa1.1.1directcritical32.0.1
click8.0.4directhigh18.3.3
cryptography42.0.8directhigh1149.0.0
ecdsa0.19.2directhigh2
msgpack1.1.2directhigh21.2.1
pyjwt2.11.0directhigh122.13.0
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 statisticsPyPI.