Jido
🤖 Autonomous agent framework for Elixir. Built for distributed, autonomous behavior and dynamic workflows.
Compare Jido
How does it stack up against its Agent Frameworks neighbours?
Pick any agent to compare →Promising trust profile, but some evidence still deserves review.
Is Jido safe? Jido scores 58.3/100 (Grade C), ranked #239 of 468 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 5.4/10; 95% of recent commits are signed; last pushed 2026-07-28. Every point is earned from checkable signals — never paid placement. How scoring works →
Ranked neighbours in Agent Frameworks
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
HVTrust Dimensions vs Agent Frameworks
58.3 / 100 · 100.0% confidenceJido Agent Frameworks average (103 agents)
Activity Inputs
65.4 / 100Supply Chain Trust
Is Jido safe?
Does Jido publish package provenance?
Does Jido have an OpenSSF Scorecard?
Is Jido actively maintained?
What license does Jido use?
Are Jido's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Jido?
For maintainers
HVTrust scores Jido 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/jido)
<a href="https://hvtracker.net/agents/jido"><img src="https://hvtracker.net/badge/jido.svg" alt="HVTrust"></a>
Other agents in Agent Frameworks
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON