updated 2026-11-05 12:09 UTC

ai-hedge-fund-crypto

Repository

AI-Hedge-Fund for Crypto 🚀 AI-powered hedge fund for cryptocurrency trading, leveraging LLM agents for intelligent decision-making.

Research & Data Python Needs review MIT

Is ai-hedge-fund-crypto safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.4 / 10
Provenance None
Signed commits 6%
Last push 426d ago
Compare ai-hedge-fund-crypto

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

Pick any agent to compare →
Suggest a correction

In detail: ai-hedge-fund-crypto scores 16.2/100 (Grade D), ranked #1373 of 1374 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 1.4/10; 6% of recent commits are signed; last pushed 2025-09-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How ai-hedge-fund-crypto could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [4.2.1] no meaningful activity in 12 months (last push 2025-09-05)

Chain of custody

Scanners check what the code says. This traces who ships ai-hedge-fund-crypto and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/51bitquant/ai-hedge-fund-crypto, MIT, last pushed 2025-09-05. 6% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 1.4/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 0

  3. Published packages None

    No registry package. ai-hedge-fund-crypto is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-26 OSSF Scorecard: 1.4/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues ai-hedge-fund-crypto’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How ai-hedge-fund-crypto compares in Research & Data

  1. #34 MindSearch 27.5 +11.3
  2. #35 Agent Laboratory 23.1 +6.9
  3. #36 DeepAnalyze 22.4 +6.2
  4. #37 ai-hedge-fund-crypto 16.2 this agent
  5. #38 InternAgent 13.2 −3.0

Bars show each HVTrust score; the tick marks ai-hedge-fund-crypto’s 16.2.

Where the 16.2 comes from

HVTrust dimensions vs the Research & Data average

16.2 / 100 · 100.0% confidence

ai-hedge-fund-crypto Research & Data average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.0 / 25
6.7 below avg 8.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.1 below avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
9.7 / 17
2.2 below avg 11.9
Maintenance60% last-push freshness · 40% commit activity
0 / 20
13.4 below avg 13.4
AdoptionLog-scaled stars · package downloads
6.7 / 20
4.1 below avg 10.8

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 25 spots (#1345 → #1370)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.4/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.
Refresh maintenance signals The repo was last pushed 426 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[4.2.1] no meaningful activity in 12 months (last push 2025-09-05)
Compare with another agent
View Research & Data Report missing data
27.0
Activity sub-score · out of 100
#37
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 D 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-11-05 12:09 UTC · Repo last pushed 426 days ago — may be stale

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
626
Forks
158
Last Push
2025-09-05
426 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
7
Rank Change
=
was #1373

Analysis

Activity Inputs

27.0 / 100
StarsRepository reach
16.8 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.2 / 20

Common questions about ai-hedge-fund-crypto

Public trust evidence for ai-hedge-fund-crypto 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 ai-hedge-fund-crypto publish package provenance?
No published build provenance is currently detected for ai-hedge-fund-crypto. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does ai-hedge-fund-crypto have an OpenSSF Scorecard?
ai-hedge-fund-crypto has an OpenSSF Scorecard score of 1.4/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 ai-hedge-fund-crypto actively maintained?
Stale. The repository has not been pushed to in 426 days. Consider whether the project is still being maintained.
What license does ai-hedge-fund-crypto use?
ai-hedge-fund-crypto ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are ai-hedge-fund-crypto's commits signed?
6% of the last 100 commits to ai-hedge-fund-crypto 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 ai-hedge-fund-crypto'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-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, Groq, OpenAI, OpenRouter
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain ai-hedge-fund-crypto?

For maintainers

HVTrust scores ai-hedge-fund-crypto 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
Rank 16HVTrust 3Warning Issued 2Surface 1Scorecard 1Delisted 1Listed 1Surface 1
2026-10-09
Rank Moved
Rank dropped 25 spots (#1345 → #1370)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, Groq, OpenAI, OpenRouter
2026-09-23
Warning Issued
Warning: eligibility issues detected
2026-09-23
HVTrust Changed
HVTrust up 5.8pts (10.4 → 16.2)
2026-09-22
Newly Listed
First tracked at rank #1319
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-06
Rank Moved
Rank dropped 45 spots (#1270 → #1315)
2026-09-06
HVTrust Changed
HVTrust down 10.0pts (26.2 → 16.2)
2026-09-05
Warning Issued
Warning: eligibility issues detected
2026-09-05
Rank Moved
Rank dropped 13 spots (#1257 → #1270)
2026-09-04
Rank Moved
Rank dropped 17 spots (#1240 → #1257)
2026-09-03
Rank Moved
Rank dropped 35 spots (#1205 → #1240)
2026-09-02
Rank Moved
Rank dropped 35 spots (#1170 → #1205)
2026-09-01
Rank Moved
Rank dropped 43 spots (#1127 → #1170)
2026-08-31
Rank Moved
Rank dropped 30 spots (#1097 → #1127)
2026-08-30
Rank Moved
Rank dropped 48 spots (#1049 → #1097)
2026-08-29
Rank Moved
Rank dropped 50 spots (#999 → #1049)
2026-08-28
Rank Moved
Rank dropped 37 spots (#962 → #999)
2026-08-27
Rank Moved
Rank dropped 26 spots (#936 → #962)
2026-08-26
Scorecard Added
OSSF Scorecard: 1.4/10
2026-08-26
Rank Moved
Rank rose 371 spots (#1307 → #936)
2026-08-26
HVTrust Changed
HVTrust up 16.0pts (10.2 → 26.2)
2026-08-16
Rank Moved
Rank dropped 25 spots (#1282 → #1307)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-10
Rank Moved
Rank dropped 79 spots (#1203 → #1282)
2026-08-08
Rank Moved
Rank dropped 682 spots (#521 → #1203)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 16.2 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/ai-hedge-fund-crypto.svg)](https://hvtracker.net/agents/ai-hedge-fund-crypto)
HTML:
<a href="https://hvtracker.net/agents/ai-hedge-fund-crypto"><img src="https://hvtracker.net/badge/ai-hedge-fund-crypto.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.4 · Raw JSON