Is chidori safe to use?

chidori has an HVTrust score of 22.9/100 (Grade D), ranked #867 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for chidori?

chidori scores 22.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.4k GitHub stars and is categorized under Agent Frameworks.

chidori

ThousandBirdsInc/chidori

The agent framework where every run is durable, replayable, and resumable by default.

Agent Frameworks Rust Grade D Listed Apache-2.0

22.9/100

Rank #867 of 1204

Compare chidori

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade D · 1/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Rank +2

Is chidori safe? chidori scores 22.9/100 (Grade D), ranked #867 of 1204 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 68% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#95 waku-agent — 23.4 (D) → #96 mcp-agent — 23.2 (D) → #98 AWorld — 22.9 (D) → #99 adk-java — 22.6 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 397 spots (#467 → #864)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-03

Newly Listed

First tracked at rank #443

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for chidori View Agent Frameworks Report missing data

72.6

Activity sub-score · out of 100

#97

In Agent Frameworks

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

Activity & Reach

Stars

1.4k

Forks

Last Push

2026-08-09

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #864

Analysis

HVTrust Dimensions vs Agent Frameworks

22.9 / 100 · 50.0% confidence

chidori Agent Frameworks average (117 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

3.4 / 25

4.8 below avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.1 below avg 11.6

Maintenance60% last-push freshness · 40% commit activity

18.6 / 20

4.3 above avg 14.3

AdoptionLog-scaled stars · package downloads

7.5 / 20

3.9 below avg 11.4

Activity Inputs

72.6 / 100

StarsRepository reach

18.8 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

20.6 / 25

CommunityFork signal

8.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

68%

of last 100 commits verified

Is chidori safe?

Public trust evidence for chidori is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does chidori publish package provenance?

No published build provenance is currently detected for chidori. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does chidori have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for chidori. 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 chidori actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does chidori use?

chidori ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are chidori's commits signed?

68% of the last 100 commits to chidori 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

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool 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

How this surface has changed

Detected changes to chidori'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-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain chidori?

For maintainers

HVTrust scores chidori 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

2026-08-08

Rank Moved

Rank dropped 397 spots (#467 → #864)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-03

Newly Listed

First tracked at rank #443

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/chidori.svg)](https://hvtracker.net/agents/chidori)
            
HTML:
            <a href="https://hvtracker.net/agents/chidori"><img src="https://hvtracker.net/badge/chidori.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON