Symphony
Symphony turns project work into isolated, autonomous implementation runs, allowing teams to manage work instead of supervising coding agents.
Is Symphony safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Symphony
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: Symphony scores 49.1/100 (Grade D), ranked #1034 of 1387 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 2.9/10; 96% of recent commits are signed; last pushed 2026-09-15. Every point is earned from checkable signals — never paid placement. How scoring works →
How Symphony 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 2.9 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +12.7 → 61.8 C · #34 of 77
Chain of custody
Scanners check what the code says. This traces who ships Symphony 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.
-
Source Signed
github.com/openai/symphony, Apache-2.0, last pushed 2026-09-15. 96% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 2.9/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies6
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 3Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 3Packaging -1Pinned-Dependencies 6SAST 0Security-Policy 0Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages None
No registry package. Symphony is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Symphony.
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 Symphony’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.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Symphony compares in Coding Agents
- #55 OpenCursor 51.1 +2.0
- #56 Aider 49.2 +0.1
- #57 Symphony 49.1 this agent
- #58 Grok Build 48.5 −0.6
- #59 Roo Code 48.3 −0.8
Bars show each HVTrust score; the tick marks Symphony’s 49.1.
Where the 49.1 comes from
HVTrust dimensions vs the Coding Agents average
49.1 / 100 · 100.0% confidenceSymphony Coding Agents average (77 agents)
Quick Trust Read
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 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
Activity & Reach
Analysis
Activity Inputs
60.0 / 100Common questions about Symphony
Does Symphony publish package provenance?
Does Symphony have an OpenSSF Scorecard?
Is Symphony actively maintained?
What license does Symphony use?
Are Symphony's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Symphony?
For maintainers
HVTrust scores Symphony 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/symphony)
<a href="https://hvtracker.net/agents/symphony"><img src="https://hvtracker.net/badge/symphony.svg" alt="HVTrust"></a>
Other agents in Coding Agents
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