FinRobot

FinRobot: An Open-Source AI Agent Platform for Financial Applications using LLMs 🚀 🚀 🚀

Research & Data Jupyter Notebook Grade C Listed Apache-2.0
52.1/100
Rank #298 of 468
Compare FinRobot

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-07-27 · 10d ago
Recent change
Rank

Is FinRobot safe? FinRobot scores 52.1/100 (Grade C), ranked #298 of 468 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 2.9/10; 86% of recent commits are signed; last pushed 2026-07-27. 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-04
Rank Moved
Rank rose 12 spots (#310 → #298)
2026-07-29
Rank Moved
Rank dropped 10 spots (#298 → #308)
2026-07-15
Rank Moved
Rank dropped 12 spots (#277 → #289)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.9/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.
72.1
Activity sub-score · out of 100
#13

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-08-06 05:30 UTC · Repo last pushed 10 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
7.7k
Forks
1.3k
Last Push
2026-07-27
10 days ago
Commits (4 wk)
6
Downloads (7d)
HN mentions (30d)
Open Issues
58
Rank Change
=
was #298

Analysis

HVTrust Dimensions vs Research & Data

52.1 / 100 · 100.0% confidence

FinRobot Research & Data average (24 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.9 / 25
in line with avg 8.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
11.0 / 17
0.7 below avg 11.7
Maintenance60% last-push freshness · 40% commit activity
14.7 / 20
2.2 above avg 12.5
AdoptionLog-scaled stars · package downloads
9.3 / 20
2.5 below avg 11.8

Activity Inputs

72.1 / 100
StarsRepository reach
23.3 / 30
FreshnessLast push recency
23.6 / 25
ActivityRecent commits
10.5 / 25
CommunityFork signal
14.5 / 20

Supply Chain Trust

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

Is FinRobot safe?

Public trust evidence for FinRobot is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does FinRobot publish package provenance?
No published build provenance is currently detected for FinRobot. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does FinRobot have an OpenSSF Scorecard?
FinRobot has an OpenSSF Scorecard score of 2.9/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 FinRobot actively maintained?
Maintained. Last push was 10 days ago.
What license does FinRobot use?
FinRobot ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are FinRobot's commits signed?
86% of the last 100 commits to FinRobot 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
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • shell
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 FinRobot?

For maintainers

HVTrust scores FinRobot 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 8HVTrust 2Listed 1Scorecard 1Score 1Grade 1
2026-08-04
Rank Moved
Rank rose 12 spots (#310 → #298)
2026-07-29
Rank Moved
Rank dropped 10 spots (#298 → #308)
2026-07-15
Rank Moved
Rank dropped 12 spots (#277 → #289)
2026-07-14
Rank Moved
Rank dropped 14 spots (#263 → #277)
2026-07-13
Rank Moved
Rank dropped 29 spots (#234 → #263)
2026-07-08
Grade Changed
Trust grade D → C
2026-07-07
Rank Moved
Rank rose 28 spots (#260 → #232)
2026-07-07
HVTrust Changed
HVTrust up 6.5pts (43.3 → 49.8)
2026-07-07
Activity Score Changed
Activity score up 18pts (55 → 72)
2026-06-24
Rank Moved
Rank dropped 31 spots (#225 → #256)
2026-06-23
Scorecard Added
OSSF Scorecard: 2.1/10
2026-06-23
Rank Moved
Rank rose 61 spots (#286 → #225)
2026-06-23
HVTrust Changed
HVTrust up 25.4pts (21.0 → 46.4)
2026-06-21
Newly Listed
First tracked at rank #283

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 52.1 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/finrobot.svg)](https://hvtracker.net/agents/finrobot)
HTML:
<a href="https://hvtracker.net/agents/finrobot"><img src="https://hvtracker.net/badge/finrobot.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