Jido

🤖 Autonomous agent framework for Elixir. Built for distributed, autonomous behavior and dynamic workflows.

Agent Frameworks Elixir Grade C Listed Apache-2.0
58.3/100
Rank #239 of 468
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.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-07-28 · 9d ago
Recent change
Rank +1

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

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-05
Rank Moved
Rank rose 29 spots (#267 → #238)
2026-08-04
Rank Moved
Rank dropped 34 spots (#233 → #267)
2026-07-28
Rank Moved
Rank rose 25 spots (#249 → #224)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.4/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.
65.4
Activity sub-score · out of 100
#48

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-08-06 05:00 UTC · Repo last pushed 9 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
1.8k
Forks
111
Last Push
2026-07-28
9 days ago
Commits (4 wk)
9
Downloads (7d)
HN mentions (30d)
Open Issues
2
Rank Change
▼1
was #238

Analysis

HVTrust Dimensions vs Agent Frameworks

58.3 / 100 · 100.0% confidence

Jido Agent Frameworks average (103 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.5 / 25
2.5 above avg 9.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
13.1 / 17
1.1 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
15.4 / 20
0.8 above avg 14.6
AdoptionLog-scaled stars · package downloads
7.8 / 20
4.1 below avg 11.9

Activity Inputs

65.4 / 100
StarsRepository reach
19.5 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
12.5 / 25
CommunityFork signal
9.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.4 / 10
OpenSSF Scorecard · scanned Aug 4, 2026
Signed Commits
95%
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 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

Is Jido safe?

Jido 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 Jido publish package provenance?
No published build provenance is currently detected for Jido. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Jido have an OpenSSF Scorecard?
Jido has an OpenSSF Scorecard score of 5.4/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 Jido actively maintained?
Maintained. Last push was 9 days ago.
What license does Jido use?
Jido ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Jido's commits signed?
95% of the last 100 commits to Jido 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
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 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
Rank 12HVTrust 4Listed 1Grade 1Scorecard 1
2026-08-05
Rank Moved
Rank rose 29 spots (#267 → #238)
2026-08-04
Rank Moved
Rank dropped 34 spots (#233 → #267)
2026-07-28
Rank Moved
Rank rose 25 spots (#249 → #224)
2026-07-26
Rank Moved
Rank dropped 33 spots (#218 → #251)
2026-07-23
Rank Moved
Rank rose 32 spots (#249 → #217)
2026-07-18
Rank Moved
Rank rose 36 spots (#283 → #247)
2026-07-18
HVTrust Changed
HVTrust up 4.8pts (52.0 → 56.8)
2026-07-17
Rank Moved
Rank dropped 39 spots (#244 → #283)
2026-07-17
HVTrust Changed
HVTrust down 4.8pts (56.8 → 52.0)
2026-07-14
Rank Moved
Rank dropped 20 spots (#224 → #244)
2026-07-13
Rank Moved
Rank dropped 25 spots (#199 → #224)
2026-07-09
Rank Moved
Rank dropped 27 spots (#177 → #204)
2026-07-09
HVTrust Changed
HVTrust down 3.0pts (58.5 → 55.5)
2026-06-24
Rank Moved
Rank dropped 18 spots (#158 → #176)
2026-06-21
Scorecard Added
OSSF Scorecard: 5.4/10
2026-06-21
Grade Changed
Trust grade D → C
2026-06-21
Rank Moved
Rank rose 99 spots (#247 → #148)
2026-06-21
HVTrust Changed
HVTrust up 35.6pts (24.7 → 60.3)
2026-06-20
Newly Listed
First tracked at rank #247

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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