Honcho

Memory library for building stateful agents

Memory & Knowledge Python Grade D Listed AGPL-3.0
40.0/100
Rank #634 of 1308
Compare Honcho

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-17 · 0d ago
Recent change
New

Is Honcho safe? Honcho scores 40.0/100 (Grade D), ranked #634 of 1308 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; 87% of recent commits are signed; last pushed 2026-08-17. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-16
Newly Listed
First tracked at rank #642
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.
82.6
Activity sub-score · out of 100
#39

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-08-17 23:32 UTC · Repo last pushed today

Rank Trend

2026-08-16 2026-08-17

Activity & Reach

Stars
6.7k
Forks
821
Last Push
2026-08-17
today
Commits (4 wk)
47
Downloads (7d)
332,767
pypi
HN mentions (30d)
Open Issues
73
Rank Change
▲8
was #642

Analysis

HVTrust Dimensions vs Memory & Knowledge

40.0 / 100 · 67.0% confidence

Honcho Memory & Knowledge average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.4 / 25
5.5 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
18.7 / 20
1.0 above avg 17.7
AdoptionLog-scaled stars · package downloads
16.5 / 20
2.9 above avg 13.6

Activity Inputs

82.6 / 100
StarsRepository reach
23.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
21.0 / 25
CommunityFork signal
13.6 / 20

Supply Chain Trust

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

Is Honcho safe?

Public trust evidence for Honcho 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 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?
No OpenSSF Scorecard data is currently published for Honcho. 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 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?
87% 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
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
5 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas 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

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
Listed 1
2026-08-16
Newly Listed
First tracked at rank #642

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 40.0 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON