Helicone

🧊 Open source LLM observability platform. One line of code to monitor, evaluate, and experiment. YC W23 🍓

Observability & Evaluation TypeScript Grade C Listed Apache-2.0
62.3/100
Rank #275 of 1204
Compare Helicone

How does it stack up against its Observability & Evaluation 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 A · 4/5 signals
Last push
2026-07-25 · 15d ago
Recent change
Rank +2

Is Helicone safe? Helicone scores 62.3/100 (Grade C), ranked #275 of 1204 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.9/10; 99% of recent commits are signed; last pushed 2026-07-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Observability & Evaluation

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-08
Rank Moved
Rank dropped 65 spots (#205 → #270)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Amazon Bedrock, Azure OpenAI, Google Gemini
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/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.
62.5
Activity sub-score · out of 100
#13

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 A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-09 19:31 UTC · Repo last pushed 15 days ago

Activity & Reach

Stars
6.0k
Forks
647
Last Push
2026-07-25
15 days ago
Commits (4 wk)
1
Downloads (7d)
248
pypi
HN mentions (30d)
4
Open Issues
49
Rank Change
▼5
was #270

Analysis

HVTrust Dimensions vs Observability & Evaluation

62.3 / 100 · 100.0% confidence

Helicone Observability & Evaluation average (22 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.1 / 25
in line with avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.3 below avg 13.1
Transparency50% declared license · 50% OSSF Scorecard
12.7 / 17
1.0 above avg 11.7
Maintenance60% last-push freshness · 40% commit activity
12.2 / 20
3.2 below avg 15.4
AdoptionLog-scaled stars · package downloads
12.3 / 20
2.0 below avg 14.3

Activity Inputs

62.5 / 100
StarsRepository reach
22.7 / 30
FreshnessLast push recency
22.9 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
13.1 / 20

Supply Chain Trust

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

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 4.9/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 15 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.

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
medium confidence
Implemented
Helicone appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Helicone's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Amazon Bedrock, Azure OpenAI, Google Gemini
2026-06-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-06-05
Provider Added
Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Azure OpenAI, Google Gemini, OpenAI, Postgres, Supabase
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Helicone?

For maintainers

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.

Reputation Timeline

Signal history
Rank 8Score 3HVTrust 2Surface 2Listed 1Grade 1Scorecard 1MCP 1Surface 1Surface 1
2026-08-08
Rank Moved
Rank dropped 65 spots (#205 → #270)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Amazon Bedrock, Azure OpenAI, Google Gemini
2026-07-21
Rank Moved
Rank rose 22 spots (#218 → #196)
2026-07-21
Activity Score Changed
Activity score up 6pts (59 → 64)
2026-07-15
Rank Moved
Rank dropped 25 spots (#193 → #218)
2026-07-14
Rank Moved
Rank dropped 14 spots (#179 → #193)
2026-07-13
Rank Moved
Rank dropped 10 spots (#169 → #179)
2026-07-12
Rank Moved
Rank dropped 10 spots (#159 → #169)
2026-06-24
Rank Moved
Rank dropped 15 spots (#155 → #170)
2026-06-14
Activity Score Changed
Activity score down 7pts (71 → 64)
2026-06-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-06-05
Provider Added
Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Azure OpenAI, Google Gemini, OpenAI, Postgres, Supabase
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-06-01
Rank Moved
Rank dropped 16 spots (#94 → #110)
2026-05-29
HVTrust Changed
HVTrust up 9.8pts (50.5 → 60.3)
2026-05-28
Activity Score Changed
Activity score up 10pts (59 → 70)
2026-05-27
Scorecard Added
OSSF Scorecard: 5.3/10
2026-05-27
Grade Changed
Trust grade D → C
2026-05-27
HVTrust Changed
HVTrust up 23.7pts (24.4 → 48.1)
2026-05-25
Newly Listed
First tracked at rank #112

Embed Badge Badge guide for maintainers →

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

Other agents in Observability & Evaluation

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON