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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed yesterday
Rank Trend
2026-06-012026-06-04
Activity & Reach
Stars
1.6k
Forks
315
Last Push
2026-06-03
yesterday
Commits (4 wk)
336
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
78
Rank Change
▼11
was #122
Analysis
HVTrust Dimensions
56.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
6.2 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.3 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
7.7 / 20
Activity Inputs
80.8 / 100
StarsRepository reach
19.3 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
11.6 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.5 / 10
via deps.dev · OpenSSF
Signed Commits
12%
of last 100 commits verified
Binary-Artifacts9
Branch-Protection6
CI-Tests7
CII-Best-Practices0
Code-Review0
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions0
Vulnerabilities4
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 4.5/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?
12% 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.
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Lumibot?
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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
