Is Maxun safe?
Maxun scores 53.3/100 (Grade C), ranked #216 of 328 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types).
The public evidence: no package-provenance attestation found;
OSSF Scorecard rates its supply-chain practices 4.0/10;
24% of recent commits are signed;
last pushed 2026-07-10. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
53.3/100 · Grade C
Strongest Signal
Maintenance
19.6/20
Weakest Signal
Safety / Integrity
6.2/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-06-24
Rank Moved
Rank dropped 12 spots (#154 → #166)
2026-06-13
Rank Moved
Rank rose 10 spots (#132 → #122)
2026-06-11
Rank Moved
Rank dropped 12 spots (#120 → #132)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 4.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
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 A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed yesterday
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
16.4k
Forks
1.4k
Last Push
2026-07-10
yesterday
Commits (4 wk)
80
Downloads (7d)
28
pypi
HN mentions (30d)
7
Open Issues
84
Rank Change
▲1
was #217
Analysis
HVTrust Dimensions
53.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
6.2 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.9 / 17
MaintenanceFreshness and commits
19.6 / 20
AdoptionStars and downloads
12.1 / 20
Activity Inputs
88.7 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
23.8 / 25
CommunityFork signal
14.6 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.0 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
24%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection1
CI-Tests0
CII-Best-Practices0
Code-Review2
Contributors10
Dangerous-Workflow-1
Dependency-Update-Tool0
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions-1
Vulnerabilities10
Is Maxun safe?
Public trust evidence for Maxun 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 Maxun publish package provenance?
No published build provenance is currently detected for Maxun. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Maxun have an OpenSSF Scorecard?
Maxun has an OpenSSF Scorecard score of 4.0/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 Maxun actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Maxun use?
Maxun ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Maxun's commits signed?
24% of the last 100 commits to Maxun 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.
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.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
browser
code
database
search
shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Warning
1 package source mismatch detected
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 Maxun'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.
Runtime surface grew — new detected provider dependencies: Anthropic, Postgres
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-06-05
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
Maintain Maxun?
HVTrust scores Maxun 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.
