Lumibot

Backtestable AI trading agents and Python algorithmic trading strategies for stocks, options, crypto, futures, forex, SE

Research & Data Python Grade C Listed GPL-3.0
56.6/100
Rank #501 of 1316
Compare Lumibot

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-02 · 0d ago
Recent change
Rank +3

Is Lumibot safe? Lumibot scores 56.6/100 (Grade C), ranked #501 of 1316 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.6/10; 18% of recent commits are signed; last pushed 2026-09-02. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-31
Rank Moved
Rank dropped 14 spots (#480 → #494)
2026-08-29
Rank Moved
Rank dropped 37 spots (#451 → #488)
2026-08-27
Rank Moved
Rank dropped 13 spots (#431 → #444)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
80.9
Activity sub-score · out of 100
#15

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-02 11:33 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-02

Activity & Reach

Stars
2.0k
Forks
388
Last Push
2026-09-02
today
Commits (4 wk)
84
Downloads (7d)
HN mentions (30d)
Open Issues
65
Rank Change
▲1
was #502

Analysis

HVTrust Dimensions vs Research & Data

56.6 / 100 · 100.0% confidence

Lumibot Research & Data average (33 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.9 / 25
0.5 above avg 7.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.8 above avg 11.5
Maintenance60% last-push freshness · 40% commit activity
19.7 / 20
6.6 above avg 13.1
AdoptionLog-scaled stars · package downloads
7.9 / 20
3.0 below avg 10.9

Activity Inputs

80.9 / 100
StarsRepository reach
19.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
24.1 / 25
CommunityFork signal
12.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.6 / 10
OpenSSF Scorecard · scanned Aug 27, 2026
Signed Commits
18%
of last 100 commits verified
Binary-Artifacts 9
Branch-Protection 8
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 10
Security-Policy 4
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 6

Is Lumibot safe?

Lumibot has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Lumibot publish package provenance?
No published build provenance is currently detected for Lumibot. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Lumibot have an OpenSSF Scorecard?
Lumibot has an OpenSSF Scorecard score of 5.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Lumibot actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Lumibot use?
Lumibot ships under GPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Lumibot's commits signed?
18% of the last 100 commits to Lumibot are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Lumibot?

For maintainers

HVTrust scores Lumibot from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 14Delisted 1Listed 1
2026-08-31
Rank Moved
Rank dropped 14 spots (#480 → #494)
2026-08-29
Rank Moved
Rank dropped 37 spots (#451 → #488)
2026-08-27
Rank Moved
Rank dropped 13 spots (#431 → #444)
2026-08-26
Rank Moved
Rank dropped 23 spots (#408 → #431)
2026-08-24
Rank Moved
Rank dropped 18 spots (#391 → #409)
2026-08-22
Rank Moved
Rank rose 16 spots (#409 → #393)
2026-08-17
Rank Moved
Rank rose 11 spots (#412 → #401)
2026-08-13
Rank Moved
Rank dropped 19 spots (#374 → #393)
2026-08-12
Rank Moved
Rank rose 10 spots (#384 → #374)
2026-08-10
Rank Moved
Rank dropped 20 spots (#363 → #383)
2026-08-08
Rank Moved
Rank dropped 90 spots (#272 → #362)
2026-07-15
Rank Moved
Rank dropped 19 spots (#241 → #260)
2026-07-13
Rank Moved
Rank dropped 30 spots (#207 → #237)
2026-06-24
Rank Moved
Rank dropped 22 spots (#168 → #190)
2026-06-21
Newly Listed
First tracked at rank #160
2026-06-09
Removed From Active Tracking
Removed from active tracking

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.6 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/lumibot.svg)](https://hvtracker.net/agents/lumibot)
HTML:
<a href="https://hvtracker.net/agents/lumibot"><img src="https://hvtracker.net/badge/lumibot.svg" alt="HVTrust"></a>

Other agents in Research & Data

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON