updated 2026-08-09 20:01 UTC

MaxKB

1Panel-dev/MaxKB

🔥 MaxKB is an open-source platform for building enterprise-grade agents. 强大易用的开源企业级智能体平台。

Agent Frameworks Python Grade C Listed GPL-3.0
61.6/100
Rank #287 of 1204
Compare MaxKB

How does it stack up against its Agent Frameworks 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-09 · 0d ago
Recent change
Rank

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

Ranked neighbours in Agent Frameworks

#39 AutoGPT — 62.6 (C) → #40 fast-agent — 62.6 (C) → #42 AG2 — 60.6 (C) → #43 Marvin — 60.5 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-08
Rank Moved
Rank dropped 69 spots (#211 → #280)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Cohere
2026-07-15
Scorecard Added
OSSF Scorecard: 6.1/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.4/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.
Compare with another agent Get email alerts for MaxKB View Agent Frameworks Report missing data
91.2
Activity sub-score · out of 100
#41
In Agent Frameworks

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-09 20:01 UTC · Repo last pushed today

Activity & Reach

Stars
22.4k
Forks
3.1k
Last Push
2026-08-09
today
Commits (4 wk)
82
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
14
Rank Change
▼7
was #280

Analysis

HVTrust Dimensions vs Agent Frameworks

61.6 / 100 · 100.0% confidence

MaxKB Agent Frameworks average (117 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.6 / 25
in line with avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
13.9 / 17
2.3 above avg 11.6
Maintenance60% last-push freshness · 40% commit activity
19.7 / 20
5.4 above avg 14.3
AdoptionLog-scaled stars · package downloads
10.4 / 20
1.0 below avg 11.4

Activity Inputs

91.2 / 100
StarsRepository reach
26.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
23.9 / 25
CommunityFork signal
16.2 / 20

Supply Chain Trust

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

Is MaxKB safe?

MaxKB 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 MaxKB publish package provenance?
No published build provenance is currently detected for MaxKB. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MaxKB have an OpenSSF Scorecard?
MaxKB has an OpenSSF Scorecard score of 6.4/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 MaxKB actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MaxKB use?
MaxKB ships under GPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MaxKB's commits signed?
11% of the last 100 commits to MaxKB 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
4 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
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 MaxKB'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: Cohere

Maintain MaxKB?

For maintainers

HVTrust scores MaxKB 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
Rank 2Listed 1HVTrust 1Grade 1Scorecard 1Surface 1
2026-08-08
Rank Moved
Rank dropped 69 spots (#211 → #280)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Cohere
2026-07-15
Scorecard Added
OSSF Scorecard: 6.1/10
2026-07-15
Grade Changed
Trust grade D → C
2026-07-15
Rank Moved
Rank rose 199 spots (#393 → #194)
2026-07-15
HVTrust Changed
HVTrust up 37.8pts (23.6 → 61.4)
2026-07-14
Newly Listed
First tracked at rank #393
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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.2 · Raw JSON