updated 2026-10-21 20:07 UTC

TradingAgents

Repository Website

TradingAgents: Multi-Agents LLM Financial Trading Framework

Multi-Agent Systems Python Listed Apache-2.0

Is TradingAgents safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.8 / 10
Provenance None
Signed commits 100%
Last push 5d ago
Compare TradingAgents

How does it stack up against its Multi-Agent Systems neighbours?

Pick any agent to compare →
Suggest a correction

In detail: TradingAgents scores 65.8/100 (Grade B), ranked #489 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.8/10; 100% of recent commits are signed; last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How TradingAgents 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

Chain of custody

Scanners check what the code says. This traces who ships TradingAgents 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 Signed

    github.com/TauricResearch/TradingAgents, Apache-2.0, last pushed 2026-10-16. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review10
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages None

    No registry package. TradingAgents 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-10-02 Provenance drift warning cleared (now: not_applicable)
  • 2026-09-23 Package-provenance drift warning: package metadata no longer clearly points at this repo

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues TradingAgents’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 TradingAgents compares in Multi-Agent Systems

  1. #7 Agency Swarm 66.6 +0.8
  2. #8 Multica 66.0 +0.2
  3. #9 TradingAgents 65.8 this agent
  4. #10 agent-swarm 65.7 −0.1
  5. #11 OpenExecutive 65.6 −0.2

Bars show each HVTrust score; the tick marks TradingAgents’s 65.8.

Where the 65.8 comes from

HVTrust dimensions vs the Multi-Agent Systems average

65.8 / 100 · 100.0% confidence

TradingAgents Multi-Agent Systems average (43 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.0 / 25
2.2 above avg 8.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.7 / 20
6.6 above avg 13.1
AdoptionLog-scaled stars · package downloads
15.7 / 20
5.5 above avg 10.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-17
Rank Moved
Rank rose 26 spots (#503 → #477)
2026-10-12
Rank Moved
Rank dropped 13 spots (#472 → #485)
2026-10-09
Rank Moved
Rank dropped 13 spots (#459 → #472)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/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.
Compare with another agent Get email alerts for TradingAgents View Multi-Agent Systems Report missing data
99.4
Activity sub-score · out of 100
#9
In Multi-Agent Systems

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

Signals refreshed 2026-10-21 20:07 UTC · Repo last pushed 5 days ago

Rank Trend

2026-09-29 2026-10-21

Activity & Reach

Stars
112.5k
Forks
21.8k
Last Push
2026-10-16
5 days ago
Commits (4 wk)
146
Downloads (7d)
480
pypi
HN mentions (30d)
—
Open Issues
41
Rank Change
▲1
was #490

Analysis

Activity Inputs

99.4 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
20 / 20

Common questions about TradingAgents

TradingAgents 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 TradingAgents publish package provenance?
No published build provenance is currently detected for TradingAgents. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does TradingAgents have an OpenSSF Scorecard?
TradingAgents has an OpenSSF Scorecard score of 4.8/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 TradingAgents actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does TradingAgents use?
TradingAgents ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are TradingAgents's commits signed?
100% of the last 100 commits to TradingAgents 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
8 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 TradingAgents'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-10-02
Drift Warning Cleared
Provenance drift warning cleared (now: not_applicable)
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, DeepSeek, Google Gemini, Groq, Mistral AI, OpenAI, OpenRouter, xAI Grok
2026-09-23
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-09-18
Provider Removed
Runtime surface shrank — no longer detected: Redis
2026-09-18
Provider Added
Runtime surface grew — new detected provider dependencies: Groq, Mistral AI

Maintain TradingAgents?

For maintainers

HVTrust scores TradingAgents 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 9HVTrust 4Grade 4Listed 2Surface 2Score 1Surface 1Delisted 1Drift 1Drift 1
2026-10-17
Rank Moved
Rank rose 26 spots (#503 → #477)
2026-10-12
Rank Moved
Rank dropped 13 spots (#472 → #485)
2026-10-09
Rank Moved
Rank dropped 13 spots (#459 → #472)
2026-10-08
Grade Changed
Trust grade C → B
2026-10-08
Rank Moved
Rank rose 42 spots (#501 → #459)
2026-10-07
Rank Moved
Rank dropped 10 spots (#491 → #501)
2026-10-06
Grade Changed
Trust grade B → C
2026-10-04
Grade Changed
Trust grade C → B
2026-10-02
Drift Warning Cleared
Provenance drift warning cleared (now: not_applicable)
2026-10-02
Rank Moved
Rank rose 154 spots (#639 → #485)
2026-10-02
HVTrust Changed
HVTrust up 4.9pts (60.0 → 64.9)
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, DeepSeek, Google Gemini, Groq, Mistral AI, OpenAI, OpenRouter, xAI Grok
2026-09-24
Rank Moved
Rank dropped 109 spots (#522 → #631)
2026-09-24
HVTrust Changed
HVTrust down 3.5pts (63.4 → 59.9)
2026-09-23
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 68 spots (#590 → #522)
2026-09-23
HVTrust Changed
HVTrust up 29.0pts (34.4 → 63.4)
2026-09-22
Newly Listed
First tracked at rank #590
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Provider Removed
Runtime surface shrank — no longer detected: Redis
2026-09-18
Provider Added
Runtime surface grew — new detected provider dependencies: Groq, Mistral AI
2026-09-18
Activity Score Changed
Activity score up 5pts (94 → 99)
2026-09-09
Rank Moved
Rank rose 37 spots (#1328 → #1291)
2026-09-09
HVTrust Changed
HVTrust up 16.7pts (12.4 → 29.1)
2026-09-08
Newly Listed
First tracked at rank #1328
GitHub → Website →

Embed Badge Badge guide for maintainers →

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

Other agents in Multi-Agent Systems

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