Honcho

Memory library for building stateful agents

Memory & Knowledge Python Listed AGPL-3.0

Is Honcho safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.6 / 10
Provenance None
Signed commits 89%
Last push today
Advisories None known
Compare Honcho

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Honcho scores 75.3/100 (Grade B), ranked #272 of 1387 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 6.6/10; 89% of recent commits are signed; no published advisory affects its latest release (honcho-ai); last pushed 2026-11-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How Honcho 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.

Chain of custody

Scanners check what the code says. This traces who ships Honcho and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/plastic-labs/honcho, AGPL-3.0, last pushed 2026-11-17. 89% 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 6.6/10 (scanned Nov 15, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions8
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 9
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 9
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 8
    Vulnerabilities 0
  3. Published packages Linked, not attested

    • PyPI honcho-ai Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: honcho-ai 2.9.0. No published advisory affects it (OSV, checked 2026-11-17).

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 6.4/10

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 Honcho’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.

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 Honcho compares in Memory & Knowledge

  1. #14 Qdrant 76.4 +1.1
  2. #15 FAISS 75.8 +0.5
  3. #16 Honcho 75.3 this agent
  4. #17 Letta 74.5 −0.8
  5. #18 RAGFlow 74.5 −0.8

Bars show each HVTrust score; the tick marks Honcho’s 75.3.

Where the 75.3 comes from

HVTrust dimensions vs the Memory & Knowledge average

75.3 / 100 · 100.0% confidence

Honcho Memory & Knowledge average (52 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.7 / 25
0.7 above avg 12.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.8 below avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
14.1 / 17
1.1 above avg 13.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
2.7 above avg 17.3
AdoptionLog-scaled stars · package downloads
15.8 / 20
2.7 above avg 13.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-22
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-10-22
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-10-22
Rank Moved
Rank rose 30 spots (#276 → #246)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.6/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.
87.4
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 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-11-17 20:09 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-17

Activity & Reach

Stars
8.2k
Forks
995
Last Push
2026-11-17
today
Commits (4 wk)
125
Downloads (7d)
66,292
pypi
HN mentions (30d)
—
Open Issues
123
Rank Change
▼3
was #269

Analysis

Activity Inputs

87.4 / 100
StarsRepository reach
23.5 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.9 / 20

Common questions about Honcho

Public supply-chain signals for Honcho are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Honcho carries less obvious unverified-evidence risk than projects with thin signals.
Does Honcho publish package provenance?
No published build provenance is currently detected for Honcho. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Honcho have an OpenSSF Scorecard?
Honcho has an OpenSSF Scorecard score of 6.6/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 Honcho actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Honcho use?
Honcho ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Honcho's commits signed?
89% of the last 100 commits to Honcho 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
Honcho appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
6 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.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 Honcho'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-22
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-10-22
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI, Postgres, Qdrant, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-05
Provider Added
Runtime surface grew — new detected provider dependency: Qdrant

Maintain Honcho?

For maintainers

HVTrust scores Honcho 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 12HVTrust 2Grade 2Surface 2MCP 2Scorecard 1Delisted 1Listed 1Surface 1
2026-10-22
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-10-22
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-10-22
Rank Moved
Rank rose 30 spots (#276 → #246)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI, Postgres, Qdrant, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 332 spots (#569 → #237)
2026-09-23
HVTrust Changed
HVTrust up 38.3pts (35.8 → 74.1)
2026-09-22
Newly Listed
First tracked at rank #569
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-07
Rank Moved
Rank dropped 14 spots (#227 → #241)
2026-09-05
Provider Added
Runtime surface grew — new detected provider dependency: Qdrant
2026-09-05
Rank Moved
Rank dropped 55 spots (#172 → #227)
2026-09-04
Rank Moved
Rank dropped 17 spots (#155 → #172)
2026-08-31
Rank Moved
Rank dropped 17 spots (#130 → #147)
2026-08-30
Scorecard Added
OSSF Scorecard: 6.4/10
2026-08-30
Grade Changed
Trust grade D → B
2026-08-30
Rank Moved
Rank rose 686 spots (#816 → #130)
2026-08-30
HVTrust Changed
HVTrust up 33.1pts (40.4 → 73.5)
2026-08-29
Rank Moved
Rank dropped 47 spots (#769 → #816)
2026-08-28
Rank Moved
Rank dropped 25 spots (#744 → #769)
2026-08-27
Rank Moved
Rank dropped 21 spots (#723 → #744)
2026-08-26
Rank Moved
Rank dropped 98 spots (#625 → #723)
2026-08-25
Rank Moved
Rank rose 11 spots (#636 → #625)

Embed Badge Badge guide for maintainers →

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

Other agents in Memory & Knowledge

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