Hive

Multi-Agent Harness for Production AI

Multi-Agent Systems Python Grade C Listed Apache-2.0
52.0/100
Rank #438 of 1283
Compare Hive

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

Pick any agent to compare →

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-08-12 · 0d ago
Recent change
Activity +1

Is Hive safe? Hive scores 52.0/100 (Grade C), ranked #438 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.1/10; 12% of recent commits are signed; last pushed 2026-08-12. 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-09
Activity Score Changed
Activity score up 16pts (57 → 73)
2026-08-08
Rank Moved
Rank dropped 138 spots (#365 → #503)
2026-07-29
Rank Moved
Rank dropped 10 spots (#327 → #337)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.1/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.
77.2
Activity sub-score · out of 100
#16

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

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
10.9k
Forks
5.7k
Last Push
2026-08-12
today
Commits (4 wk)
6?
Downloads (7d)
HN mentions (30d)
Open Issues
900
Rank Change
=
was #438

Analysis

HVTrust Dimensions vs Multi-Agent Systems

52.0 / 100 · 100.0% confidence

Hive Multi-Agent Systems average (35 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.7 / 25
0.5 below 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.0 / 17
1.0 above avg 11.0
Maintenance60% last-push freshness · 40% commit activity
13.7 / 20
0.7 above avg 13.0
AdoptionLog-scaled stars · package downloads
9.7 / 20
in line with avg 10.0

Activity Inputs

77.2 / 100
StarsRepository reach
24.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
10.5 / 25
CommunityFork signal
17.5 / 20

Supply Chain Trust

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

Is Hive safe?

Public trust evidence for Hive 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 Hive publish package provenance?
No published build provenance is currently detected for Hive. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Hive have an OpenSSF Scorecard?
Hive has an OpenSSF Scorecard score of 4.1/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 Hive actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Hive use?
Hive ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Hive's commits signed?
12% of the last 100 commits to Hive 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
high confidence
Implemented
Hive 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: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
  • browser
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 Hive'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: Multi-provider (LiteLLM)

Maintain Hive?

For maintainers

HVTrust scores Hive 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 1Grade 1Surface 1Score 1
2026-08-09
Activity Score Changed
Activity score up 16pts (57 → 73)
2026-08-08
Rank Moved
Rank dropped 138 spots (#365 → #503)
2026-07-29
Rank Moved
Rank dropped 10 spots (#327 → #337)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)
2026-07-15
Rank Moved
Rank dropped 23 spots (#292 → #315)
2026-07-14
Rank Moved
Rank dropped 13 spots (#279 → #292)
2026-07-13
Rank Moved
Rank dropped 34 spots (#245 → #279)
2026-06-28
Grade Changed
Trust grade C → D
2026-06-24
Newly Listed
First tracked at rank #229

Embed Badge Badge guide for maintainers →

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