updated 2026-08-17 00:02 UTC

Ouroboros (Agent OS)

Q00/ouroboros

Agent OS: the agent gets smarter on its own. We just hold the line: the grading command and expected result never make i

Coding Agents Python Grade D Listed MIT
42.6/100
Rank #588 of 1308
Compare Ouroboros (Agent OS)

How does it stack up against its Coding Agents 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 C · 2/5 signals
Last push
2026-08-16 · 1d ago
Recent change
New

Is Ouroboros (Agent OS) safe? Ouroboros (Agent OS) scores 42.6/100 (Grade D), ranked #588 of 1308 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 91% of recent commits are signed; last pushed 2026-08-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#45 Integuru — 44.6 (D) → #46 GPT Pilot — 43.1 (D) → #48 DeepSeek Harness — 42.6 (D) → #49 Sweep — 41.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-16
Newly Listed
First tracked at rank #586
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 Ouroboros (Agent OS) View Coding Agents Report missing data
85.2
Activity sub-score · out of 100
#47
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 D 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-17 00:02 UTC · Repo last pushed yesterday

Activity & Reach

Stars
5.5k
Forks
553
Last Push
2026-08-16
yesterday
Commits (4 wk)
364
Downloads (7d)
30,798
pypi
HN mentions (30d)
—
Open Issues
49
Rank Change
▼2
was #586

Analysis

HVTrust Dimensions vs Coding Agents

42.6 / 100 · 67.0% confidence

Ouroboros (Agent OS) Coding Agents average (70 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.6 / 25
2.9 below avg 7.5
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
2.5 below avg 11.0
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
4.6 above avg 15.3
AdoptionLog-scaled stars · package downloads
15.0 / 20
2.7 above avg 12.3

Activity Inputs

85.2 / 100
StarsRepository reach
22.4 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
91%
of last 100 commits verified

Is Ouroboros (Agent OS) safe?

Public trust evidence for Ouroboros (Agent OS) 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 Ouroboros (Agent OS) publish package provenance?
No published build provenance is currently detected for Ouroboros (Agent OS). This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Ouroboros (Agent OS) have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Ouroboros (Agent OS). 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 Ouroboros (Agent OS) actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Ouroboros (Agent OS) use?
Ouroboros (Agent OS) ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ouroboros (Agent OS)'s commits signed?
91% of the last 100 commits to Ouroboros (Agent OS) 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
high confidence
Implemented
Ouroboros (Agent OS) appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • 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 Ouroboros (Agent OS)?

For maintainers

HVTrust scores Ouroboros (Agent OS) 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
Listed 1
2026-08-16
Newly Listed
First tracked at rank #586
GitHub → PyPI: ouroboros-ai

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 42.6 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/ouroboros-agent-os.svg)](https://hvtracker.net/agents/ouroboros-agent-os)
HTML:
<a href="https://hvtracker.net/agents/ouroboros-agent-os"><img src="https://hvtracker.net/badge/ouroboros-agent-os.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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