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-04 18:04 UTC·Repo last pushed 9 days ago
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
8.9k
Forks
1.0k
Last Push
2026-05-26
9 days ago
Commits (4 wk)
16
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
72
Rank Change
▼15
was #113
Analysis
HVTrust Dimensions
59.0 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
9.0 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.4 / 17
MaintenanceFreshness and commits
16.3 / 20
AdoptionStars and downloads
9.5 / 20
Activity Inputs
76.8 / 100
StarsRepository reach
23.7 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
15.3 / 25
CommunityFork signal
14.0 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.8 / 10
via deps.dev · OpenSSF
Signed Commits
35%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection1
CI-Tests0
CII-Best-Practices0
Code-Review5
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy10
Signed-Releases-1
Token-Permissions9
Vulnerabilities0
Is UFO safe?
UFO 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 UFO publish package provenance?
No published build provenance is currently detected for UFO. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does UFO have an OpenSSF Scorecard?
UFO has an OpenSSF Scorecard score of 5.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 UFO actively maintained?
Maintained. Last push was 9 days ago.
What license does UFO use?
UFO ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are UFO's commits signed?
35% of the last 100 commits to UFO 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain UFO?
HVTrust scores UFO 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) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
