MaiBot

MaiSaka, an LLM-based intelligent agent, is a digital lifeform devoted to understanding you and interacting in the style

Voice & Conversational Python Grade C Listed GPL-3.0
56.5/100
Rank #720 of 1328
Compare MaiBot

How does it stack up against its Voice & Conversational 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-09-20 · 0d ago
Recent change
Rank

Is MaiBot safe? MaiBot scores 56.5/100 (Grade C), ranked #720 of 1328 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 4.1/10; 12% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Voice & Conversational

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-19
Rank Moved
Rank rose 16 spots (#736 → #720)
2026-09-07
Rank Moved
Rank dropped 40 spots (#674 → #714)
2026-09-05
Rank Moved
Rank dropped 86 spots (#580 → #666)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.1/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.
85.7
Activity sub-score · out of 100
#7

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

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars
6.0k
Forks
633
Last Push
2026-09-20
today
Commits (4 wk)
123
Downloads (7d)
HN mentions (30d)
Open Issues
58
Rank Change
=
was #720

Analysis

HVTrust Dimensions vs Voice & Conversational

56.5 / 100 · 100.0% confidence

MaiBot Voice & Conversational average (13 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.7 / 25
4.1 below avg 9.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.7 below avg 12.5
Transparency50% declared license · 50% OSSF Scorecard
12.0 / 17
in line with avg 12.1
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
3.5 above avg 16.5
AdoptionLog-scaled stars · package downloads
9.1 / 20
1.7 below avg 10.8

Activity Inputs

85.7 / 100
StarsRepository reach
22.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.0 / 20

Supply Chain Trust

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

Is MaiBot safe?

MaiBot 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 MaiBot publish package provenance?
No published build provenance is currently detected for MaiBot. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MaiBot have an OpenSSF Scorecard?
MaiBot has an OpenSSF Scorecard score of 4.1/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 MaiBot actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MaiBot use?
MaiBot ships under GPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MaiBot's commits signed?
12% of the last 100 commits to MaiBot 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.

Compare MaiBot head-to-head

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
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
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

Maintain MaiBot?

For maintainers

HVTrust scores MaiBot 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 17Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-19
Rank Moved
Rank rose 16 spots (#736 → #720)
2026-09-07
Rank Moved
Rank dropped 40 spots (#674 → #714)
2026-09-05
Rank Moved
Rank dropped 86 spots (#580 → #666)
2026-09-04
Rank Moved
Rank dropped 15 spots (#565 → #580)
2026-09-03
Rank Moved
Rank dropped 50 spots (#515 → #565)
2026-09-02
Rank Moved
Rank dropped 17 spots (#498 → #515)
2026-09-01
Rank Moved
Rank dropped 16 spots (#482 → #498)
2026-08-31
Rank Moved
Rank dropped 30 spots (#452 → #482)
2026-08-30
Scorecard Added
OSSF Scorecard: 4.1/10
2026-08-30
Grade Changed
Trust grade D → C
2026-08-30
Rank Moved
Rank rose 635 spots (#1087 → #452)
2026-08-30
HVTrust Changed
HVTrust up 33.3pts (23.5 → 56.8)
2026-08-29
Rank Moved
Rank dropped 40 spots (#1047 → #1087)
2026-08-28
Rank Moved
Rank dropped 31 spots (#1016 → #1047)
2026-08-27
Rank Moved
Rank dropped 20 spots (#996 → #1016)
2026-08-26
Rank Moved
Rank dropped 92 spots (#904 → #996)
2026-08-24
Rank Moved
Rank dropped 13 spots (#891 → #904)
2026-08-16
Rank Moved
Rank dropped 19 spots (#892 → #911)
2026-08-10
Rank Moved
Rank dropped 52 spots (#839 → #891)
2026-08-08
Rank Moved
Rank dropped 372 spots (#462 → #834)
2026-08-06
Newly Listed
First tracked at rank #455

Embed Badge Badge guide for maintainers →

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

Other agents in Voice & Conversational

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