updated 2026-08-12 05:32 UTC

Symphony

openai/symphony

Symphony turns project work into isolated, autonomous implementation runs, allowing teams to manage work instead of supe

Coding Agents Elixir Grade C Listed Apache-2.0
57.6/100
Rank #375 of 1283
Compare Symphony

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-07-24 · 19d ago
Recent change
Rank +1

Is Symphony safe? Symphony scores 57.6/100 (Grade C), ranked #375 of 1283 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 3.4/10; 91% of recent commits are signed; last pushed 2026-07-24. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#32 Pi — 58.0 (C) → #33 Ponytail — 57.7 (C) → #35 OpenCursor — 55.9 (C) → #36 Aider — 55.1 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 20 spots (#354 → #374)
2026-08-08
Rank Moved
Rank dropped 87 spots (#265 → #352)
2026-07-28
Rank Moved
Rank dropped 10 spots (#231 → #241)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.4/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 Symphony View Coding Agents Report missing data
81.5
Activity sub-score · out of 100
#34
In Coding Agents

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 →

Signals refreshed 2026-08-12 05:32 UTC · Repo last pushed 19 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
26.5k
Forks
2.7k
Last Push
2026-07-24
19 days ago
Commits (4 wk)
20
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▼2
was #373

Analysis

HVTrust Dimensions vs Coding Agents

57.6 / 100 · 100.0% confidence

Symphony Coding Agents average (67 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.8 / 25
1.1 above avg 7.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
11.4 / 17
in line with avg 11.1
Maintenance60% last-push freshness · 40% commit activity
16.0 / 20
0.8 above avg 15.2
AdoptionLog-scaled stars · package downloads
10.6 / 20
1.6 below avg 12.2

Activity Inputs

81.5 / 100
StarsRepository reach
26.5 / 30
FreshnessLast push recency
22.4 / 25
ActivityRecent commits
16.5 / 25
CommunityFork signal
16.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.4 / 10
OpenSSF Scorecard · scanned Aug 10, 2026
Signed Commits
91%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 6
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Symphony safe?

Symphony 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 Symphony publish package provenance?
No published build provenance is currently detected for Symphony. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Symphony have an OpenSSF Scorecard?
Symphony has an OpenSSF Scorecard score of 3.4/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 Symphony actively maintained?
Maintained. Last push was 19 days ago.
What license does Symphony use?
Symphony ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Symphony's commits signed?
91% of the last 100 commits to Symphony 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
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 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 9Listed 1Score 1HVTrust 1
2026-08-10
Rank Moved
Rank dropped 20 spots (#354 → #374)
2026-08-08
Rank Moved
Rank dropped 87 spots (#265 → #352)
2026-07-28
Rank Moved
Rank dropped 10 spots (#231 → #241)
2026-07-20
Rank Moved
Rank rose 21 spots (#241 → #220)
2026-07-17
Rank Moved
Rank rose 48 spots (#290 → #242)
2026-07-17
HVTrust Changed
HVTrust up 5.6pts (51.6 → 57.2)
2026-07-17
Activity Score Changed
Activity score up 15pts (62 → 77)
2026-07-15
Rank Moved
Rank dropped 21 spots (#269 → #290)
2026-07-14
Rank Moved
Rank dropped 14 spots (#255 → #269)
2026-07-13
Rank Moved
Rank dropped 30 spots (#225 → #255)
2026-07-01
Rank Moved
Rank dropped 10 spots (#202 → #212)
2026-06-24
Newly Listed
First tracked at rank #196
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Coding Agents

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