Orkas

Open-source multi-agent AI desktop client — build and command your AI agent team through conversation. A commander LLM d

Multi-Agent Systems TypeScript Grade C Listed MIT
59.0/100
Rank #484 of 1320
Compare Orkas

How does it stack up against its Multi-Agent Systems neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Rank +7

Is Orkas safe? Orkas scores 59.0/100 (Grade C), ranked #484 of 1320 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 4.5/10; 29% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-03
Rank Moved
Rank rose 15 spots (#490 → #475)
2026-09-02
Rank Moved
Rank dropped 11 spots (#479 → #490)
2026-09-01
Rank Moved
Rank dropped 10 spots (#469 → #479)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.5/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
78.1
Activity sub-score · out of 100
#15

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 →

Signals refreshed 2026-09-04 23:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
1.7k
Forks
75
Last Push
2026-09-04
today
Commits (4 wk)
103
Downloads (7d)
HN mentions (30d)
Open Issues
2
Rank Change
▼9
was #475

Analysis

HVTrust Dimensions vs Multi-Agent Systems

59.0 / 100 · 100.0% confidence

Orkas Multi-Agent Systems average (36 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.1 / 25
0.9 below avg 8.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.2
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
in line with avg 11.9
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.6 above avg 12.4
AdoptionLog-scaled stars · package downloads
7.8 / 20
2.0 below avg 9.8

Activity Inputs

78.1 / 100
StarsRepository reach
19.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
8.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.5 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
29%
of last 100 commits verified
Binary-Artifacts 8
Branch-Protection 0
CI-Tests 7
CII-Best-Practices 0
Code-Review 7
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 10
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 10
Vulnerabilities 0

Is Orkas safe?

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

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
Rank 16Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-03
Rank Moved
Rank rose 15 spots (#490 → #475)
2026-09-02
Rank Moved
Rank dropped 11 spots (#479 → #490)
2026-09-01
Rank Moved
Rank dropped 10 spots (#469 → #479)
2026-08-31
Rank Moved
Rank dropped 26 spots (#443 → #469)
2026-08-28
Scorecard Added
OSSF Scorecard: 4.2/10
2026-08-28
Grade Changed
Trust grade D → C
2026-08-28
Rank Moved
Rank rose 541 spots (#984 → #443)
2026-08-28
HVTrust Changed
HVTrust up 32.5pts (24.4 → 56.9)
2026-08-27
Rank Moved
Rank dropped 25 spots (#959 → #984)
2026-08-26
Rank Moved
Rank dropped 89 spots (#870 → #959)
2026-08-25
Rank Moved
Rank rose 24 spots (#894 → #870)
2026-08-22
Rank Moved
Rank rose 13 spots (#912 → #899)
2026-08-21
Rank Moved
Rank rose 21 spots (#933 → #912)
2026-08-20
Rank Moved
Rank dropped 17 spots (#916 → #933)
2026-08-19
Rank Moved
Rank dropped 13 spots (#903 → #916)
2026-08-17
Rank Moved
Rank rose 16 spots (#920 → #904)
2026-08-16
Rank Moved
Rank dropped 16 spots (#904 → #920)
2026-08-15
Rank Moved
Rank dropped 26 spots (#878 → #904)
2026-08-12
Rank Moved
Rank rose 14 spots (#881 → #867)
2026-08-10
Newly Listed
First tracked at rank #906

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 59.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/orkas.svg)](https://hvtracker.net/agents/orkas)
HTML:
<a href="https://hvtracker.net/agents/orkas"><img src="https://hvtracker.net/badge/orkas.svg" alt="HVTrust"></a>

Other agents in Multi-Agent Systems

Data sources
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