BettaFish

微舆:人人可用的多Agent舆情分析助手,打破信息茧房,还原舆情原貌,预测未来走向,辅助决策!从0实现,不依赖任何框架。

Multi-Agent Systems Python Grade C Listed GPL-2.0
55.1/100
Rank #412 of 1283
Compare BettaFish

How does it stack up against its Multi-Agent Systems 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-10 · 1d ago
Recent change
Rank +1

Is BettaFish safe? BettaFish scores 55.1/100 (Grade C), ranked #412 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 4.8/10; 22% of recent commits are signed; last pushed 2026-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

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 14 spots (#399 → #413)
2026-08-08
Rank Moved
Rank dropped 94 spots (#293 → #387)
2026-07-20
Grade Changed
Trust grade D → C
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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
87.7
Activity sub-score · out of 100
#14

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 21:02 UTC · Repo last pushed yesterday

Activity & Reach

Stars
42.0k
Forks
7.6k
Last Push
2026-08-10
yesterday
Commits (4 wk)
22
Downloads (7d)
HN mentions (30d)
Open Issues
1
Rank Change
▲1
was #413

Analysis

HVTrust Dimensions vs Multi-Agent Systems

55.1 / 100 · 100.0% confidence

BettaFish Multi-Agent Systems average (35 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.1 / 25
0.9 above avg 6.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.2
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
1.6 above avg 11.0
Maintenance60% last-push freshness · 40% commit activity
17.4 / 20
4.4 above avg 13.0
AdoptionLog-scaled stars · package downloads
11.1 / 20
1.1 above avg 10.0

Activity Inputs

87.7 / 100
StarsRepository reach
27.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
17.0 / 25
CommunityFork signal
18.1 / 20

Supply Chain Trust

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

Is BettaFish safe?

BettaFish 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 BettaFish publish package provenance?
No published build provenance is currently detected for BettaFish. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does BettaFish have an OpenSSF Scorecard?
BettaFish 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 BettaFish actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does BettaFish use?
BettaFish ships under GPL-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are BettaFish's commits signed?
22% of the last 100 commits to BettaFish 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
high confidence
3 tags
Broad capability areas detected.
  • browser
  • database
  • search
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 BettaFish'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-07-17
Provider Added
Runtime surface grew — new detected provider dependency: DeepSeek

Maintain BettaFish?

For maintainers

HVTrust scores BettaFish 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 5HVTrust 2Listed 1Scorecard 1Surface 1Score 1Grade 1
2026-08-10
Rank Moved
Rank dropped 14 spots (#399 → #413)
2026-08-08
Rank Moved
Rank dropped 94 spots (#293 → #387)
2026-07-20
Grade Changed
Trust grade D → C
2026-07-20
Rank Moved
Rank rose 68 spots (#337 → #269)
2026-07-20
HVTrust Changed
HVTrust up 9.7pts (44.7 → 54.4)
2026-07-20
Activity Score Changed
Activity score up 24pts (63 → 87)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: DeepSeek
2026-07-15
Rank Moved
Rank dropped 23 spots (#308 → #331)
2026-07-14
Scorecard Added
OSSF Scorecard: 4.4/10
2026-07-14
Rank Moved
Rank rose 62 spots (#370 → #308)
2026-07-14
HVTrust Changed
HVTrust up 29.0pts (16.5 → 45.5)
2026-07-13
Newly Listed
First tracked at rank #370

Embed Badge Badge guide for maintainers →

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