updated 2026-09-29 16:10 UTC

Octop

Repository Website by TencentCloud

A smarter, self-hosted AI assistant — multi-user, multi-agent.

Multi-Agent Systems Python Listed MIT

Is Octop safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result
Provenance None
Signed commits 58%
Last push today
Advisories None known
Compare Octop

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

Pick any agent to compare →
Suggest a correction

In detail: Octop scores 34.3/100 (Grade D), ranked #1259 of 1343 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 58% of recent commits are signed; no published advisory affects its latest release (octop); last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

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

How Octop compares in Multi-Agent Systems

  1. #30 tribe 37.8 +3.5
  2. #31 GPTSwarm 37.4 +3.1
  3. #32 Octop 34.3 this agent
  4. #33 MetaGPT 32.9 −1.4
  5. #34 KaibanJS 32.7 −1.6

Bars show each HVTrust score; the tick marks Octop’s 34.3.

Where the 34.3 comes from

HVTrust dimensions vs the Multi-Agent Systems average

34.3 / 100 · 67.0% confidence

Octop Multi-Agent Systems average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.9 / 25
5.1 below avg 8.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.2
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.4 below avg 11.9
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.2 above avg 12.8
AdoptionLog-scaled stars · package downloads
13.3 / 20
3.2 above avg 10.1

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-29
Newly Listed
First tracked at rank #1259
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 Octop View Multi-Agent Systems Report missing data
85.9
Activity sub-score · out of 100
#32
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 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-09-29 16:10 UTC · Repo last pushed today

Activity & Reach

Stars
5.7k
Forks
714
Last Push
2026-09-29
today
Commits (4 wk)
316
Downloads (7d)
1,646
pypi
HN mentions (30d)
—
Open Issues
326
Rank Change
NEW

Analysis

Activity Inputs

85.9 / 100
StarsRepository reach
22.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
58%
of last 100 commits verified

Common questions about Octop

Public trust evidence for Octop 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 Octop publish package provenance?
No published build provenance is currently detected for Octop. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Octop have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Octop. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Octop actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Octop use?
Octop ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Octop's commits signed?
57% of the last 100 commits to Octop 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
  • database
  • shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Octop?

For maintainers

HVTrust scores Octop 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
Listed 1
2026-09-29
Newly Listed
First tracked at rank #1259
GitHub → Website → PyPI: octop

Embed Badge Badge guide for maintainers →

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

Other agents in Multi-Agent Systems

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON