Is Agent Orchestrator safe to use?

Agent Orchestrator has an HVTrust score of 63.3/100 (Grade C), ranked #77 of 385 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Agent Orchestrator?

Agent Orchestrator scores 63.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 13.2k GitHub stars and is categorized under Agent Skills.

Agent Orchestrator

Repository

Website

Run and supervise teams of coding agents from planning to merge. Any harness (Claude code, codex, +25 more). Desktop, web, mobile, and cloud agents.

Agent Skills Go Listed Apache-2.0

Is Agent Orchestrator safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.5 / 10

Provenance None

Signed commits 100%

Last push today

Compare Agent Orchestrator

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Agent Orchestrator scores 63.3/100 (Grade C), ranked #77 of 385 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; 100% of recent commits are signed; last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Agent Orchestrator 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.

Raise the OSSF Scorecard from 4.5 to 9.0lowest checks: CII-Best-Practices 0, Dependency-Update-Tool 0, SAST 0 +9.4 → 72.7 B · #27 of 385

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Agent Orchestrator 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 and, for skills, AST02 Supply Chain Compromise.

Source Signed

github.com/Untrivial-ai/agent-orchestrator, Apache-2.0, last pushed 2026-10-16. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.5/10 (scanned Oct 14, 2026). The checks that decide who can get a change released:
- Code Review7
- Branch Protection1
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies3
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 1

CI-Tests 10

CII-Best-Practices 0

Code-Review 7

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 10

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages None

No registry package. Agent Orchestrator is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-08-31 OSSF Scorecard: 4.8/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Agent Orchestrator’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 Agent Orchestrator compares in Agent Skills

Bars show each HVTrust score; the tick marks Agent Orchestrator’s 63.3.

Where the 63.3 comes from

HVTrust dimensions vs the Agent Skills average

63.3 / 100 · 100.0% confidence

Agent Orchestrator Agent Skills average (385 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

10.6 / 25

2.8 above avg 7.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

12.3 / 17

in line with avg 12.0

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.9 above avg 14.1

AdoptionLog-scaled stars · package downloads

9.9 / 20

0.9 above avg 9.0

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-13

Rank Moved

Rank rose 12 spots (#83 → #71)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Grade Changed

Trust grade D → C

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.

Compare with another agent Get email alerts for Agent Orchestrator View Agent Skills Report missing data

89.9

Activity sub-score · out of 100

#77

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

2026-09-29 2026-10-16

Activity & Reach

Stars

13.2k

Forks

1.8k

Last Push

2026-10-16

today

Commits (4 wk)

562

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

476

Rank Change

▼4

was #73

Analysis

Activity Inputs

89.9 / 100

StarsRepository reach

24.7 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

15.2 / 20

Common questions about Agent Orchestrator

Agent Orchestrator 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 Agent Orchestrator publish package provenance?

No published build provenance is currently detected for Agent Orchestrator. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Agent Orchestrator have an OpenSSF Scorecard?

Agent Orchestrator 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 Agent Orchestrator actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Agent Orchestrator use?

Agent Orchestrator ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Agent Orchestrator's commits signed?

100% of the last 100 commits to Agent Orchestrator 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

None detected

No MCP server signal detected.

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

Declared

Declared 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

How this surface has changed

Detected changes to Agent Orchestrator'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

Maintain Agent Orchestrator?

For maintainers

HVTrust scores Agent Orchestrator 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

2026-10-13

Rank Moved

Rank rose 12 spots (#83 → #71)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 31 spots (#43 → #74)

2026-09-23

HVTrust Changed

HVTrust up 13.1pts (49.5 → 62.6)

2026-09-22

Newly Listed

First tracked at rank #43

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-14

Rank Moved

Rank dropped 10 spots (#61 → #71)

2026-09-05

Rank Moved

Rank dropped 12 spots (#39 → #51)

2026-08-31

Scorecard Added

OSSF Scorecard: 4.8/10

2026-08-31

Grade Changed

Trust grade D → C

2026-08-31

Rank Moved

Rank rose 190 spots (#224 → #34)

2026-08-31

HVTrust Changed

HVTrust up 37.1pts (26.7 → 63.8)

2026-08-30

Rank Moved

Rank dropped 38 spots (#186 → #224)

2026-08-29

Rank Moved

Rank dropped 37 spots (#149 → #186)

2026-08-28

Rank Moved

Rank dropped 25 spots (#124 → #149)

2026-08-27

Rank Moved

Rank dropped 22 spots (#102 → #124)

2026-08-26

Rank Moved

Rank dropped 62 spots (#40 → #102)

2026-08-11

Newly Listed

First tracked at rank #37

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/agent-orchestrator.svg)](https://hvtracker.net/agents/agent-orchestrator)
            
HTML:
            <a href="https://hvtracker.net/agents/agent-orchestrator"><img src="https://hvtracker.net/badge/agent-orchestrator.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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.4 · Raw JSON

Agent Orchestrator

How Agent Orchestrator could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Agent Orchestrator compares in Agent Skills

Where the 63.3 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Agent Orchestrator

AI agent surface

Maintain Agent Orchestrator?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills