Maxun

Turn any website into a structured API. Extract, automate, search and monitor the web.

Research & Data TypeScript Listed AGPL-3.0

Is Maxun safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.7 / 10
Provenance None
Signed commits 36%
Last push yesterday
Advisories None known
Compare Maxun
Suggest a correction

In detail: Maxun scores 62.3/100 (Grade C), ranked #596 of 1371 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.7/10; 36% of recent commits are signed; no published advisory affects its latest release (maxun); last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Maxun 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 Maxun 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 Partly signed

    github.com/getmaxun/maxun, AGPL-3.0, last pushed 2026-10-08. 36% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.7/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:

    • Code Review3
    • Branch Protection1
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 1
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 3
    Contributors 10
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 10
  3. Published packages Not linked

    • PyPI maxun Source link points to getmaxun/python-sdk, same owner 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: maxun 0.0.13. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

  • 2026-08-07 Provenance drift warning cleared (now: unknown)

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues Maxun’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 Maxun compares in Research & Data

  1. #10 open-science 62.5 +0.2
  2. #11 EvoScientist 62.3 ±0
  3. #12 Maxun 62.3 this agent
  4. #13 OpenBB 60.5 −1.8
  5. #14 SurfSense 58.8 −3.5

Bars show each HVTrust score; the tick marks Maxun’s 62.3.

Where the 62.3 comes from

HVTrust dimensions vs the Research & Data average

62.3 / 100 · 100.0% confidence

Maxun Research & Data average (37 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.7 / 25
in line with avg 7.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
12.5 / 17
1.2 above avg 11.3
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.2 above avg 12.7
AdoptionLog-scaled stars · package downloads
12.5 / 20
2.0 above avg 10.5

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 21 spots (#575 → #596)
2026-10-03
Rank Moved
Rank rose 14 spots (#582 → #568)
2026-10-02
Rank Moved
Rank rose 23 spots (#605 → #582)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.7/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.
90.3
Activity sub-score · out of 100
#12

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 refreshed 2026-10-09 08:15 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
17.7k
Forks
1.5k
Last Push
2026-10-08
yesterday
Commits (4 wk)
196
Downloads (7d)
49
pypi
HN mentions (30d)
6
Open Issues
73
Rank Change
▼21
was #575

Analysis

Activity Inputs

90.3 / 100
StarsRepository reach
25.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.8 / 20

Common questions about Maxun

Maxun 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 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.7/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?
36% 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.

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: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
2 tags
Broad capability areas detected.
  • browser
  • database
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
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.

2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)

Maintain Maxun?

For maintainers

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.

Reputation Timeline

Signal history
Rank 38Drift 1
2026-10-09
Rank Moved
Rank dropped 21 spots (#575 → #596)
2026-10-03
Rank Moved
Rank rose 14 spots (#582 → #568)
2026-10-02
Rank Moved
Rank rose 23 spots (#605 → #582)
2026-09-27
Rank Moved
Rank dropped 12 spots (#589 → #601)
2026-09-24
Rank Moved
Rank dropped 27 spots (#563 → #590)
2026-09-23
Rank Moved
Rank dropped 341 spots (#222 → #563)
2026-09-21
Rank Moved
Rank rose 334 spots (#557 → #223)
2026-09-20
Rank Moved
Rank rose 15 spots (#572 → #557)
2026-09-18
Rank Moved
Rank rose 12 spots (#585 → #573)
2026-09-17
Rank Moved
Rank dropped 36 spots (#549 → #585)
2026-09-14
Rank Moved
Rank rose 14 spots (#561 → #547)
2026-09-12
Rank Moved
Rank rose 51 spots (#609 → #558)
2026-09-11
Rank Moved
Rank dropped 11 spots (#598 → #609)
2026-09-10
Rank Moved
Rank dropped 55 spots (#543 → #598)
2026-09-09
Rank Moved
Rank dropped 10 spots (#533 → #543)
2026-09-07
Rank Moved
Rank dropped 28 spots (#505 → #533)
2026-09-06
Rank Moved
Rank dropped 21 spots (#484 → #505)
2026-09-05
Rank Moved
Rank dropped 65 spots (#419 → #484)
2026-09-03
Rank Moved
Rank dropped 22 spots (#388 → #410)
2026-09-01
Rank Moved
Rank dropped 11 spots (#376 → #387)
2026-08-31
Rank Moved
Rank dropped 32 spots (#344 → #376)
2026-08-30
Rank Moved
Rank rose 10 spots (#354 → #344)
2026-08-29
Rank Moved
Rank dropped 10 spots (#344 → #354)
2026-08-26
Rank Moved
Rank dropped 27 spots (#305 → #332)
2026-08-24
Rank Moved
Rank dropped 25 spots (#275 → #300)
2026-08-23
Rank Moved
Rank rose 20 spots (#295 → #275)
2026-08-22
Rank Moved
Rank rose 12 spots (#307 → #295)
2026-08-17
Rank Moved
Rank rose 13 spots (#313 → #300)
2026-08-16
Rank Moved
Rank dropped 10 spots (#303 → #313)
2026-08-13
Rank Moved
Rank dropped 18 spots (#286 → #304)
2026-08-12
Rank Moved
Rank rose 17 spots (#303 → #286)
2026-08-10
Rank Moved
Rank dropped 19 spots (#285 → #304)
2026-08-08
Rank Moved
Rank dropped 73 spots (#209 → #282)
2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)
2026-07-29
Rank Moved
Rank dropped 10 spots (#268 → #278)
2026-07-16
Rank Moved
Rank rose 16 spots (#273 → #257)
2026-07-15
Rank Moved
Rank dropped 12 spots (#261 → #273)
2026-07-14
Rank Moved
Rank dropped 15 spots (#246 → #261)
2026-07-13
Rank Moved
Rank dropped 30 spots (#216 → #246)

Embed Badge Badge guide for maintainers →

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

Other agents in Research & Data

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