updated 2026-11-15 04:07 UTC

Ouroboros (Agent OS)

Repository Website

Agent OS: the agent gets smarter on its own. We just hold the line: Interview-gated, staged evaluation, budgeted evolution loop. MCP server, 14 runtimes: Claude Code, Codex CLI, Gemini CLI, OpenCode, Copilot, Kiro and more.

Coding Agents Python Listed MIT

Is Ouroboros (Agent OS) safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.8 / 10
Provenance None
Signed commits 100%
Last push 2d ago
Advisories None known
Compare Ouroboros (Agent OS)

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Ouroboros (Agent OS) scores 74.8/100 (Grade B), ranked #280 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.8/10; 100% of recent commits are signed; no published advisory affects its latest release (ouroboros-ai); last pushed 2026-11-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Ouroboros (Agent OS) could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Ouroboros (Agent OS) and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/Q00/ouroboros, MIT, last pushed 2026-11-13. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.8/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection8
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 8
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI ouroboros-ai Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: ouroboros-ai 0.60.0. No published advisory affects it (OSV, checked 2026-11-14).

Changes to this chain

  • 2026-09-05 OSSF Scorecard: 5.4/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Ouroboros (Agent OS)’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Ouroboros (Agent OS) compares in Coding Agents

  1. #9 CodeWhale 81.9 +7.1
  2. #10 Gemini CLI 77.3 +2.5
  3. #11 Ouroboros (Agent OS) 74.8 this agent
  4. #12 OpenHands 74.5 −0.3
  5. #13 DeepSeek Harness 72.1 −2.7

Bars show each HVTrust score; the tick marks Ouroboros (Agent OS)’s 74.8.

Where the 74.8 comes from

HVTrust dimensions vs the Coding Agents average

74.8 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.2 / 25
3.1 above avg 9.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
13.4 / 17
1.4 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
5.3 above avg 14.6
AdoptionLog-scaled stars · package downloads
15.1 / 20
2.9 above avg 12.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.8/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.
Compare with another agent
View Coding Agents Report missing data
85.7
Activity sub-score · out of 100
#11
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 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 refreshed 2026-11-15 04:07 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars
6.4k
Forks
637
Last Push
2026-11-13
2 days ago
Commits (4 wk)
241
Downloads (7d)
31,718
pypi
HN mentions (30d)
—
Open Issues
72
Rank Change
=
was #280

Analysis

Activity Inputs

85.7 / 100
StarsRepository reach
22.8 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.0 / 20

Common questions about Ouroboros (Agent OS)

Ouroboros (Agent OS) 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 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?
Ouroboros (Agent OS) has an OpenSSF Scorecard score of 5.8/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 Ouroboros (Agent OS) actively maintained?
Actively maintained. The repository was pushed to within the last 2 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?
100% 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
How this surface has changed

Detected changes to Ouroboros (Agent OS)'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-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, Multi-provider (LiteLLM), OpenAI, OpenRouter
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

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
Rank 15HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1Surface 1
2026-10-08
Rank Moved
Rank dropped 12 spots (#243 → #255)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, Multi-provider (LiteLLM), OpenAI, OpenRouter
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 342 spots (#596 → #254)
2026-09-23
HVTrust Changed
HVTrust up 39.2pts (34.1 → 73.3)
2026-09-22
Newly Listed
First tracked at rank #596
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 13 spots (#260 → #247)
2026-09-11
Rank Moved
Rank dropped 10 spots (#240 → #250)
2026-09-05
Scorecard Added
OSSF Scorecard: 5.4/10
2026-09-05
Grade Changed
Trust grade D → B
2026-09-05
Rank Moved
Rank rose 777 spots (#1005 → #228)
2026-09-05
HVTrust Changed
HVTrust up 30.9pts (42.3 → 73.2)
2026-09-04
Rank Moved
Rank dropped 23 spots (#982 → #1005)
2026-09-03
Rank Moved
Rank dropped 68 spots (#914 → #982)
2026-09-02
Rank Moved
Rank dropped 54 spots (#860 → #914)
2026-09-01
Rank Moved
Rank dropped 29 spots (#831 → #860)
2026-08-31
Rank Moved
Rank dropped 26 spots (#805 → #831)
2026-08-30
Rank Moved
Rank dropped 28 spots (#777 → #805)
2026-08-29
Rank Moved
Rank dropped 46 spots (#731 → #777)
2026-08-28
Rank Moved
Rank dropped 27 spots (#704 → #731)
2026-08-27
Rank Moved
Rank dropped 19 spots (#685 → #704)
2026-08-26
Rank Moved
Rank dropped 98 spots (#587 → #685)
GitHub → Website → PyPI: ouroboros-ai

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 74.8 Grade B
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON