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. Full methodology →
Signals refreshed2026-06-24 18:00 UTC·Repo last pushed 15 days ago
Activity & Reach
Stars
25.6k
Forks
2.6k
Last Push
2026-06-09
15 days ago
Commits (4 wk)
8
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
NEW
Analysis
HVTrust Dimensions
57.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
9.3 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.7 / 17
MaintenanceFreshness and commits
14.8 / 20
AdoptionStars and downloads
10.6 / 20
Activity Inputs
77.3 / 100
StarsRepository reach
26.4 / 30
FreshnessLast push recency
22.9 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
15.9 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.8 / 10
OpenSSF Scorecard · scanned Jun 24, 2026
Signed Commits
91%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection0
CI-Tests10
CII-Best-Practices0
Code-Review2
Contributors3
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies5
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
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.8/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 15 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
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
OpenAI
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
code
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?
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.
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 v3.2 · Raw JSON
