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 20:15 UTC·Repo last pushed 17 days ago
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
5.8k
Forks
593
Last Push
2026-05-18
17 days ago
Commits (4 wk)
5
Downloads (7d)
—
HN mentions (30d)
4
Open Issues
104
Rank Change
▼11
was #117
Analysis
HVTrust Dimensions
58.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.6 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.0 / 17
MaintenanceFreshness and commits
14.0 / 20
AdoptionStars and downloads
9.0 / 20
Activity Inputs
68.0 / 100
StarsRepository reach
22.6 / 30
FreshnessLast push recency
22.6 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
12.9 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.3 / 10
via deps.dev · OpenSSF
Signed Commits
99%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection6
CI-Tests10
CII-Best-Practices0
Code-Review3
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is Helicone safe?
Helicone 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 Helicone publish package provenance?
No published build provenance is currently detected for Helicone. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Helicone have an OpenSSF Scorecard?
Helicone has an OpenSSF Scorecard score of 5.3/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 Helicone actively maintained?
Maintained. Last push was 17 days ago.
What license does Helicone use?
Helicone ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Helicone's commits signed?
99% of the last 100 commits to Helicone 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 Helicone?
HVTrust scores Helicone 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 · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
