updated 2026-10-10 20:07 UTC

OmniRoute

Repository Website

Never stop coding. Free MIT AI gateway: one endpoint, 359 providers (150+ free), 1200+ models Kimi, Claude, GPT, Gemini, GLM, DeepSeek, MiniMax. Works with Claude Code, Codex, Cursor, OpenCode, Cline & Copilot. Quota-aware auto-fallback, RTK+Caveman compression saves 15-95% tokens, MCP/A2A…

Agent Skills TypeScript Listed MIT

Is OmniRoute safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.5 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare OmniRoute

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: OmniRoute scores 92.4/100 (Grade A), ranked #1 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.5/10; 100% of recent commits are signed; no published advisory affects its latest release (omniroute); last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How OmniRoute 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 OmniRoute 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 and, for skills, AST02 Supply Chain Compromise.

  1. Source Signed

    github.com/diegosouzapw/OmniRoute, MIT, last pushed 2026-10-10. 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 6.5/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked and attested

    • npm omniroute Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: omniroute 3.8.51. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected

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 OmniRoute’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 the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How OmniRoute compares in Agent Skills

  1. #1 OmniRoute 92.4 this agent
  2. #2 Vercel Skills 90.1 −2.3
  3. #3 Notebooklm Py 89.3 −3.1
  4. #4 Larksuite Cli 89.0 −3.4
  5. #5 Avoid Ai Writing 88.8 −3.6

Bars show each HVTrust score; the tick marks OmniRoute’s 92.4.

Where the 92.4 comes from

HVTrust dimensions vs the Agent Skills average

92.4 / 100 · 100.0% confidence

OmniRoute Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.6 / 25
12.8 above avg 7.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.6 above avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
14.0 / 17
2.0 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.9 above avg 14.1
AdoptionLog-scaled stars · package downloads
17.9 / 20
8.9 above avg 9.0

Quick Trust Read

What Would Improve It
Improve transparency to lift the weakest part of the trust profile.
Recent Changes
2026-09-30
Grade Changed
Trust grade C → A
2026-09-30
Rank Moved
Rank rose 60 spots (#61 → #1)
2026-09-30
HVTrust Changed
HVTrust up 28.1pts (64.9 → 93.0)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.5/10. Tighten the weakest checks to improve public safety evidence.
Compare with Vercel Skills Get email alerts for OmniRoute View Agent Skills Report missing data
98.0
Activity sub-score · out of 100
#1
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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-10-10 20:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
74.9k
Forks
10.8k
Last Push
2026-10-10
today
Commits (4 wk)
1880
Downloads (7d)
44,224
npm
HN mentions (30d)
—
Open Issues
35
Rank Change
=
was #1

Analysis

Activity Inputs

98.0 / 100
StarsRepository reach
29.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
18.8 / 20

Common questions about OmniRoute

Public supply-chain signals for OmniRoute are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but OmniRoute carries less obvious unverified-evidence risk than projects with thin signals.
Does OmniRoute publish package provenance?
Yes. OmniRoute's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does OmniRoute have an OpenSSF Scorecard?
OmniRoute has an OpenSSF Scorecard score of 6.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 OmniRoute actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does OmniRoute use?
OmniRoute ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OmniRoute's commits signed?
100% of the last 100 commits to OmniRoute 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.

Compare OmniRoute head-to-head

OmniRoute vs Vercel Skills → OmniRoute vs Notebooklm Py → OmniRoute vs Larksuite Cli →

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
OmniRoute appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 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.
  • browser
  • code
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 OmniRoute'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 dependency: OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-11
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI

Maintain OmniRoute?

For maintainers

HVTrust scores OmniRoute 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
HVTrust 4Rank 4Grade 4Listed 2Surface 2Delisted 1Provenance 1MCP 1Surface 1
2026-09-30
Grade Changed
Trust grade C → A
2026-09-30
Rank Moved
Rank rose 60 spots (#61 → #1)
2026-09-30
HVTrust Changed
HVTrust up 28.1pts (64.9 → 93.0)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 168 spots (#169 → #1)
2026-09-23
HVTrust Changed
HVTrust up 55.3pts (38.1 → 93.4)
2026-09-22
Newly Listed
First tracked at rank #169
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-05
Grade Changed
Trust grade C → A
2026-09-05
Rank Moved
Rank rose 46 spots (#47 → #1)
2026-09-05
HVTrust Changed
HVTrust up 31.2pts (62.1 → 93.3)
2026-09-02
Grade Changed
Trust grade A → C
2026-09-02
Rank Moved
Rank dropped 41 spots (#1 → #42)
2026-09-02
HVTrust Changed
HVTrust down 31.4pts (93.5 → 62.1)
2026-08-26
Newly Listed
First tracked at rank #1
GitHub → Website → npm: omniroute

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON