Is Lumibot safe to use?

Lumibot has an HVTrust score of 56.8/100 (Grade C), ranked #363 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Lumibot?

Lumibot scores 56.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.9k GitHub stars and is categorized under Research & Data.

Lumibot

Lumiwealth/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.8/100

Rank #363 of 1204

Compare Lumibot

How does it stack up against its Research & Data neighbours?

Pick any agent to compare →

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-08-07 · 2d ago

Recent change

Rank +2

Is Lumibot safe? Lumibot scores 56.8/100 (Grade C), ranked #363 of 1204 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-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

#10 OpenBB — 60.5 (C) → #11 SurfSense — 58.4 (C) → #13 FinRobot — 49.3 (D) → #14 MiroThinker — 45.7 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 90 spots (#272 → #362)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → none

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)

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.

Compare with another agent Get email alerts for Lumibot View Research & Data Report missing data

81.3

Activity sub-score · out of 100

#12

In Research & Data

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 →

Activity & Reach

Stars

1.9k

Forks

363

Last Push

2026-08-07

2 days ago

Commits (4 wk)

100

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #362

Analysis

HVTrust Dimensions vs Research & Data

56.8 / 100 · 100.0% confidence

Lumibot Research & Data average (30 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.9 / 25

1.3 above avg 6.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.7 below avg 11.5

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

2.2 above avg 11.1

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.6 above avg 12.3

AdoptionLog-scaled stars · package downloads

7.9 / 20

3.2 below avg 11.1

Activity Inputs

81.3 / 100

StarsRepository reach

19.7 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

11.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.6 / 10

OpenSSF Scorecard · scanned Aug 9, 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 2 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

How this surface has changed

Detected changes to Lumibot's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → none

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Google Gemini, OpenAI, Postgres

2026-06-01

Activity Resumed

Activity resumed

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-08

Rank Moved

Rank dropped 90 spots (#272 → #362)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → none

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)

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

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Google Gemini, OpenAI, Postgres

2026-06-01

Scorecard Added

OSSF Scorecard: 4.5/10

2026-06-01

Activity Resumed

Activity resumed

2026-06-01

Grade Changed

Trust grade D → C

2026-06-01

Rank Moved

Rank rose 74 spots (#189 → #115)

2026-06-01

HVTrust Changed

HVTrust up 56.9pts (0.0 → 56.9)

2026-06-01

Activity Score Changed

Activity score up 81pts (0 → 81)

2026-05-31

Newly Listed

First tracked at rank #189

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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.2 · Raw JSON