Odysseus
Self-hosted AI workspace.
Is Odysseus safe? Promising trust profile, but some evidence still deserves review.
Compare Odysseus
How does it stack up against its UI & App Builders neighbours?
Pick any agent to compare →In detail: Odysseus scores 67.3/100 (Grade B), ranked #435 of 1378 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 7.8/10; 28% of recent commits are signed; last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →
What Odysseus can reach, and who runs it
Checked 2026-10-09, each with its source. PUBLISHER is the company's or project's own statement, which we haven't verified; CHECKED is something we observed ourselves. These facts describe the product. They don't change its score.
What it can reach
- PUBLISHER A self-hosted workspace whose agents can use local or API models, tools, MCP, files and a shell.
Security practice
- PUBLISHER Its README advises keeping authentication on, setting LOCALHOST_BYPASS=false outside local development, and not exposing raw model or service ports publicly.
- CHECKED The repository has a SECURITY.md and GitHub private vulnerability reporting is enabled.
How Odysseus 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.
- Sign every commit28% signed today +3.6 → 70.9 B · #7 of 18
- Raise the OSSF Scorecard from 7.8 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Fuzzing 0 +2.5 → 69.8 B · #7 of 18
Chain of custody
Scanners check what the code says. This traces who ships Odysseus and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/odysseus-dev/odysseus, AGPL-3.0, last pushed 2026-10-16. 28% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Strong
OpenSSF Scorecard rates the repository's practices 7.8/10 (scanned Oct 13, 2026). The checks that decide who can get a change released:
- Code Review7
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies7
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests 10CII-Best-Practices 0Code-Review 7Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 7SAST 10Security-Policy 4Signed-Releases -1Token-Permissions 10Vulnerabilities 10 -
Published packages None
No registry package. Odysseus is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Odysseus.
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Odysseus’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.
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 Odysseus compares in UI & App Builders
- #6 LibreChat 73.0 +5.7
- #7 Cherry Studio 67.4 +0.1
- #8 Odysseus 67.3 this agent
- #9 Dyad 63.4 −3.9
- #10 ToolJet 62.4 −4.9
Bars show each HVTrust score; the tick marks Odysseus’s 67.3.
Where the 67.3 comes from
HVTrust dimensions vs the UI & App Builders average
67.3 / 100 · 100.0% confidenceOdysseus UI & App Builders average (18 agents)
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 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
94.7 / 100Common questions about Odysseus
Does Odysseus publish package provenance?
Does Odysseus have an OpenSSF Scorecard?
Is Odysseus actively maintained?
What license does Odysseus use?
Are Odysseus'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.
Compare Odysseus head-to-head
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 →
- shell
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Odysseus?
For maintainers
HVTrust scores Odysseus 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/odysseus)
<a href="https://hvtracker.net/agents/odysseus"><img src="https://hvtracker.net/badge/odysseus.svg" alt="HVTrust"></a>
Other agents in UI & App Builders
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON