updated 2026-10-06 07:06 UTC

Mistral Vibe

Repository

Minimal CLI coding agent by Mistral

Coding Agents Python Listed Apache-2.0

Is Mistral Vibe safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.8 / 10
Provenance Attested
Signed commits 75%
Last push yesterday
Advisories None known
Compare Mistral Vibe

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Mistral Vibe scores 84.2/100 (Grade A), ranked #98 of 1346 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.8/10; 75% of recent commits are signed; no published advisory affects its latest release (mistral-vibe); last pushed 2026-10-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How Mistral Vibe 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Mistral Vibe 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/mistralai/mistral-vibe, Apache-2.0, last pushed 2026-10-05. 75% 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 5.8/10 (scanned Sep 26, 2026). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection1
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions8
    • Pinned Dependencies10
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 1
    CI-Tests 9
    CII-Best-Practices 0
    Code-Review 9
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 10
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 8
    Vulnerabilities 3

  3. Published packages Linked and attested

    • PyPI mistral-vibe Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: mistral-vibe 2.25.8. No published advisory affects it (OSV, checked 2026-10-05).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Mistral Vibe.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Mistral Vibe’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.

Signed credential (JSON) How to verify

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 Mistral Vibe compares in Coding Agents

  1. #5 Qwen Code 88.0 +3.8
  2. #6 CodeWhale 87.5 +3.3
  3. #7 Mistral Vibe 84.2 this agent
  4. #8 Hermes Agent 84.0 −0.2
  5. #9 oh-my-pi 83.6 −0.6

Bars show each HVTrust score; the tick marks Mistral Vibe’s 84.2.

Where the 84.2 comes from

HVTrust dimensions vs the Coding Agents average

84.2 / 100 · 100.0% confidence

Mistral Vibe Coding Agents average (75 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.5 / 25
9.4 above avg 9.1
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.2 above avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
13.4 / 17
1.5 above avg 11.9
Maintenance60% last-push freshness · 40% commit activity
13.8 / 20
1.0 below avg 14.8
AdoptionLog-scaled stars · package downloads
16.5 / 20
4.3 above avg 12.2

Quick Trust Read

What Would Improve It
Improve maintenance to lift the weakest part of the trust profile.
Recent Changes
2026-09-26
Rank Moved
Rank dropped 24 spots (#58 → #82)
2026-09-21
Rank Moved
Rank rose 25 spots (#73 → #48)
2026-09-20
Rank Moved
Rank dropped 18 spots (#55 → #73)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.8/10. Tighten the weakest checks to improve public safety evidence.
Compare with Cline Get email alerts for Mistral Vibe View Coding Agents Report missing data
72.4
Activity sub-score · out of 100
#7
In Coding Agents

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-06 07:06 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-06

Activity & Reach

Stars
5.0k
Forks
724
Last Push
2026-10-05
yesterday
Commits (4 wk)
8?
Downloads (7d)
498,368
pypi
HN mentions (30d)
—
Open Issues
170
Rank Change
▼1
was #97

Analysis

Activity Inputs

72.4 / 100
StarsRepository reach
22.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
13.3 / 20

Common questions about Mistral Vibe

Public supply-chain signals for Mistral Vibe are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Mistral Vibe carries less obvious unverified-evidence risk than projects with thin signals.
Does Mistral Vibe publish package provenance?
Yes. Mistral Vibe's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Mistral Vibe have an OpenSSF Scorecard?
Mistral Vibe has an OpenSSF Scorecard score of 5.8/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 Mistral Vibe actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Mistral Vibe use?
Mistral Vibe ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Mistral Vibe's commits signed?
75% of the last 100 commits to Mistral Vibe 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 Mistral Vibe head-to-head

Mistral Vibe vs Cline → Mistral Vibe vs Codex → Mistral Vibe vs Bernstein →

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
high confidence
Implemented
Mistral Vibe appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • code
  • shell
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
How this surface has changed

Detected changes to Mistral Vibe'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-09-03
Tool Surface Changed
Detected tool/plugin surface changed: none → declared

Maintain Mistral Vibe?

For maintainers

HVTrust scores Mistral Vibe 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 7Surface 1
2026-09-26
Rank Moved
Rank dropped 24 spots (#58 → #82)
2026-09-21
Rank Moved
Rank rose 25 spots (#73 → #48)
2026-09-20
Rank Moved
Rank dropped 18 spots (#55 → #73)
2026-09-18
Rank Moved
Rank rose 29 spots (#82 → #53)
2026-09-17
Rank Moved
Rank dropped 26 spots (#56 → #82)
2026-09-13
Rank Moved
Rank rose 28 spots (#84 → #56)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-03
Rank Moved
Rank dropped 11 spots (#57 → #68)
GitHub → PyPI: mistral-vibe

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 84.2 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/mistral-vibe.svg)](https://hvtracker.net/agents/mistral-vibe)
HTML:
<a href="https://hvtracker.net/agents/mistral-vibe"><img src="https://hvtracker.net/badge/mistral-vibe.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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