Vibe-Trading

"Vibe-Trading: Your Personal Trading Agent"

Research & Data Python Grade C Listed MIT
63.3/100
Rank #268 of 1283
Compare Vibe-Trading

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-11 · 0d ago
Recent change
Rank +1

Is Vibe-Trading safe? Vibe-Trading scores 63.3/100 (Grade C), ranked #268 of 1283 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.4/10; 36% of recent commits are signed; last pushed 2026-08-11. 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-10
Rank Moved
Rank dropped 19 spots (#247 → #266)
2026-08-08
Rank Moved
Rank dropped 50 spots (#204 → #254)
2026-08-01
Rank Moved
Rank rose 15 spots (#198 → #183)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.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.
94.1
Activity sub-score · out of 100
#8

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-11 20:02 UTC · Repo last pushed today

Activity & Reach

Stars
30.6k
Forks
4.9k
Last Push
2026-08-11
today
Commits (4 wk)
815
Downloads (7d)
HN mentions (30d)
Open Issues
8
Rank Change
▼2
was #266

Analysis

HVTrust Dimensions vs Research & Data

63.3 / 100 · 100.0% confidence

Vibe-Trading Research & Data average (31 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.6 / 25
2.2 above avg 6.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.7 below avg 11.5
Transparency50% declared license · 50% OSSF Scorecard
13.1 / 17
2.1 above avg 11.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.5 above avg 12.5
AdoptionLog-scaled stars · package downloads
10.8 / 20
in line with avg 10.9

Activity Inputs

94.1 / 100
StarsRepository reach
26.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.2 / 20

Supply Chain Trust

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

Is Vibe-Trading safe?

Vibe-Trading 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 Vibe-Trading publish package provenance?
No published build provenance is currently detected for Vibe-Trading. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Vibe-Trading have an OpenSSF Scorecard?
Vibe-Trading has an OpenSSF Scorecard score of 5.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 Vibe-Trading actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Vibe-Trading use?
Vibe-Trading ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Vibe-Trading's commits signed?
36% of the last 100 commits to Vibe-Trading 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.

Compare Vibe-Trading head-to-head

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
high confidence
Implemented
Vibe-Trading appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 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

Maintain Vibe-Trading?

For maintainers

HVTrust scores Vibe-Trading 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 5Listed 1
2026-08-10
Rank Moved
Rank dropped 19 spots (#247 → #266)
2026-08-08
Rank Moved
Rank dropped 50 spots (#204 → #254)
2026-08-01
Rank Moved
Rank rose 15 spots (#198 → #183)
2026-07-30
Rank Moved
Rank dropped 17 spots (#181 → #198)
2026-07-14
Rank Moved
Rank dropped 15 spots (#157 → #172)
2026-07-13
Newly Listed
First tracked at rank #157

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/vibe-trading.svg)](https://hvtracker.net/agents/vibe-trading)
HTML:
<a href="https://hvtracker.net/agents/vibe-trading"><img src="https://hvtracker.net/badge/vibe-trading.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.3 · Raw JSON