updated 2026-10-12 00:08 UTC

Maestro Orchestrate

Repository Website

Multi-agent orchestration platform for Gemini CLI, Claude Code, Codex, and Qwen Code — 39 specialists, parallel subagents, persistent sessions, and built-in code review, debugging, security, SEO, accessibility, and compliance tools

Agent Skills JavaScript Listed Apache-2.0

Is Maestro Orchestrate safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.9 / 10
Provenance None
Signed commits 53%
Last push yesterday
Advisories None known
Compare Maestro Orchestrate

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Maestro Orchestrate scores 57.7/100 (Grade C), ranked #127 of 371 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 3.9/10; 53% of recent commits are signed; no published advisory affects its latest release (@josstei/maestro); last pushed 2026-10-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How Maestro Orchestrate 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 Maestro Orchestrate 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 Partly signed

    github.com/josstei/maestro-orchestrate, Apache-2.0, last pushed 2026-10-11. 53% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.9/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked, not attested

    • npm @josstei/maestro Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @josstei/maestro 1.6.4. No published advisory affects it (OSV, checked 2026-10-11).

Changes to this chain

  • 2026-08-29 OSSF Scorecard: 4.1/10

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 Maestro Orchestrate’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 Maestro Orchestrate compares in Agent Skills

  1. #125 Styleseed 58.0 +0.3
  2. #126 Auto claude code research in sleep 57.8 +0.1
  3. #127 Maestro Orchestrate 57.7 this agent
  4. #128 Skillshare 57.6 −0.1
  5. #129 Spellbook 57.5 −0.2

Bars show each HVTrust score; the tick marks Maestro Orchestrate’s 57.7.

Where the 57.7 comes from

HVTrust dimensions vs the Agent Skills average

57.7 / 100 · 100.0% confidence

Maestro Orchestrate Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.5 / 25
in line with avg 7.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
11.8 / 17
in line with avg 12.1
Maintenance60% last-push freshness · 40% commit activity
12.9 / 20
1.2 below avg 14.1
AdoptionLog-scaled stars · package downloads
9.5 / 20
0.5 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-11
Rank Moved
Rank rose 16 spots (#143 → #127)
2026-10-11
Activity Score Changed
Activity score up 6pts (48 → 54)
2026-10-07
Rank Moved
Rank rose 57 spots (#204 → #147)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.9/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 Maestro Orchestrate View Agent Skills Report missing data
54.4
Activity sub-score · out of 100
#127
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 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-12 00:08 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
465
Forks
38
Last Push
2026-10-11
yesterday
Commits (4 wk)
2?
Downloads (7d)
203
npm
HN mentions (30d)
—
Open Issues
6
Rank Change
=
was #127

Analysis

Activity Inputs

54.4 / 100
StarsRepository reach
16.0 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
7.4 / 20

Common questions about Maestro Orchestrate

Maestro Orchestrate 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 Maestro Orchestrate publish package provenance?
No published build provenance is currently detected for Maestro Orchestrate. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Maestro Orchestrate have an OpenSSF Scorecard?
Maestro Orchestrate has an OpenSSF Scorecard score of 3.9/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 Maestro Orchestrate actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Maestro Orchestrate use?
Maestro Orchestrate ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Maestro Orchestrate's commits signed?
53% of the last 100 commits to Maestro Orchestrate 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
Maestro Orchestrate appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 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.
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 Maestro Orchestrate'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 dependencies: Anthropic, Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Maestro Orchestrate?

For maintainers

HVTrust scores Maestro Orchestrate 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
Rank 15HVTrust 4Listed 2Grade 2Score 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
2026-10-11
Rank Moved
Rank rose 16 spots (#143 → #127)
2026-10-11
Activity Score Changed
Activity score up 6pts (48 → 54)
2026-10-07
Rank Moved
Rank rose 57 spots (#204 → #147)
2026-10-07
HVTrust Changed
HVTrust up 3.9pts (52.7 → 56.6)
2026-10-07
Activity Score Changed
Activity score up 8pts (40 → 48)
2026-10-01
Rank Moved
Rank dropped 10 spots (#199 → #209)
2026-09-30
Rank Moved
Rank dropped 14 spots (#185 → #199)
2026-09-25
Rank Moved
Rank dropped 17 spots (#165 → #182)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 159 spots (#323 → #164)
2026-09-23
HVTrust Changed
HVTrust up 30.8pts (23.1 → 53.9)
2026-09-22
Newly Listed
First tracked at rank #323
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Grade Changed
Trust grade D → C
2026-09-11
Rank Moved
Rank rose 152 spots (#297 → #145)
2026-09-11
HVTrust Changed
HVTrust up 18.3pts (36.3 → 54.6)
2026-09-10
Rank Moved
Rank dropped 11 spots (#286 → #297)
2026-09-03
Rank Moved
Rank dropped 13 spots (#237 → #250)
2026-09-02
Rank Moved
Rank dropped 13 spots (#224 → #237)
2026-09-01
Rank Moved
Rank dropped 13 spots (#211 → #224)
2026-08-31
Rank Moved
Rank dropped 17 spots (#194 → #211)
2026-08-30
Rank Moved
Rank dropped 32 spots (#162 → #194)
2026-08-29
Scorecard Added
OSSF Scorecard: 4.1/10
2026-08-29
Rank Moved
Rank rose 78 spots (#240 → #162)
2026-08-29
HVTrust Changed
HVTrust up 16.0pts (20.8 → 36.8)
2026-08-28
Rank Moved
Rank dropped 16 spots (#224 → #240)
2026-08-26
Newly Listed
First tracked at rank #218
GitHub → Website → npm: @josstei/maestro

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 57.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/maestro-orchestrate.svg)](https://hvtracker.net/agents/maestro-orchestrate)
HTML:
<a href="https://hvtracker.net/agents/maestro-orchestrate"><img src="https://hvtracker.net/badge/maestro-orchestrate.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