Is Maestro Orchestrate safe to use?

Maestro Orchestrate has an HVTrust score of 11.2/100 (Grade D), ranked #308 of 331 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Maestro Orchestrate?

Maestro Orchestrate scores 11.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 459 GitHub stars and is categorized under Agent Skills.

Maestro Orchestrate

josstei/maestro-orchestrate

Pending first signal refresh

Agent Skills JavaScript Grade D Listed

11.2/100

Rank #308 of 331

Compare Maestro Orchestrate

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade D · 1/5 signals

Last push

2026-08-07 · 19d ago

Recent change

New

Is Maestro Orchestrate safe? Maestro Orchestrate scores 11.2/100 (Grade D), ranked #308 of 331 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#306 Guizang Social Card Skill — 11.3 (D) → #307 Debug Agent — 11.2 (D) → #309 Agentic SEO Skill — 11.0 (D) → #310 Superseo Skills — 10.8 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-26

Newly Listed

First tracked at rank #308

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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.

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

45.6

Activity sub-score · out of 100

#308

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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

459

Forks

Last Push

2026-08-07

19 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

NEW

Analysis

HVTrust Dimensions vs Agent Skills

11.2 / 100 · 40.0% confidence

Maestro Orchestrate Agent Skills average (331 agents)

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

0 / 25

1.7 below avg 1.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 11.1

Transparency50% declared license · 50% OSSF Scorecard

0 / 17

4.4 below avg 4.4

Maintenance60% last-push freshness · 40% commit activity

10.7 / 20

3.8 below avg 14.5

AdoptionLog-scaled stars · package downloads

6.4 / 20

1.9 below avg 8.3

Activity Inputs

45.6 / 100

StarsRepository reach

16.0 / 30

FreshnessLast push recency

22.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

7.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

—

Unable to query

Is Maestro Orchestrate safe?

Public trust evidence for Maestro Orchestrate is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

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?

No OpenSSF Scorecard data is currently published for Maestro Orchestrate. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is Maestro Orchestrate actively maintained?

Maintained. Last push was 19 days ago.

What license does Maestro Orchestrate use?

Maestro Orchestrate ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

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

None detected

No clear plugin system or broad tool 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 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

2026-08-26

Newly Listed

First tracked at rank #308

GitHub → npm: @josstei/maestro

Embed Badge Badge guide for maintainers →

For maintainers

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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON