Orkas
Orkas is an open-source, local-first AI desktop app: a commander LLM directs specialist sub-agents, and runs your installed coding CLIs — Claude Code, Codex, OpenCode, OpenClaw, Hermes — as local sessions. Agents self-evolve via reflection and skill crystallization. BYO keys. macOS / Windows /…
Is Orkas safe? Promising trust profile, but some evidence still deserves review.
Compare Orkas
How does it stack up against its Multi-Agent Systems neighbours?
Pick any agent to compare →In detail: Orkas scores 60.9/100 (Grade C), ranked #611 of 1325 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.2/10; 33% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How Orkas compares in Multi-Agent Systems
- #11 Agency Agents 63.6 +2.7
- #12 Open Multi-Agent 61.7 +0.8
- #13 Orkas 60.9 this agent
- #14 TradingAgents 60.0 −0.9
- #15 Rowboat 59.6 −1.3
Bars show each HVTrust score; the tick marks Orkas’s 60.9.
Where the 60.9 comes from
HVTrust dimensions vs the Multi-Agent Systems average
60.9 / 100 · 100.0% confidenceOrkas Multi-Agent Systems average (38 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 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
79.0 / 100Supply Chain Trust
Common questions about Orkas
Does Orkas publish package provenance?
Does Orkas have an OpenSSF Scorecard?
Is Orkas actively maintained?
What license does Orkas use?
Are Orkas'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.
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 →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Orkas'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.
Maintain Orkas?
For maintainers
HVTrust scores Orkas 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/orkas)
<a href="https://hvtracker.net/agents/orkas"><img src="https://hvtracker.net/badge/orkas.svg" alt="HVTrust"></a>
Other agents in Multi-Agent Systems
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON