How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 refreshed2026-07-07 22:30 UTC·Repo last pushed 4 days ago
Activity & Reach
Stars
4.6k
Forks
580
Last Push
2026-07-03
4 days ago
Commits (4 wk)
12
Downloads (7d)
182,262
pypi
HN mentions (30d)
—
Open Issues
178
Rank Change
NEW
Analysis
HVTrust Dimensions
73.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.9 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
16.2 / 20
AdoptionStars and downloads
15.8 / 20
Activity Inputs
73.2 / 100
StarsRepository reach
22.0 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
13.9 / 25
CommunityFork signal
12.9 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
67%
of last 100 commits verified
Is Mistral Vibe safe?
Mistral Vibe 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 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?
No OpenSSF Scorecard data is currently published for Mistral Vibe. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Mistral Vibe actively maintained?
Actively maintained. The repository was pushed to within the last 4 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?
67% 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.
AI agent 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 →
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
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Extensions
Extension based 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
Maintain Mistral Vibe?
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.
