Traceroot

TraceRoot - open-source observability and self-improving layer for AI agents. YC S25

Observability & Evaluation TypeScript Grade C Listed NOASSERTION
61.4/100
Rank #311 of 1308
Compare Traceroot

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 C · 2/5 signals
Last push
2026-08-18 · 1d ago
Recent change
Rank +3

Is Traceroot safe? Traceroot scores 61.4/100 (Grade C), ranked #311 of 1308 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 7.2/10; 31% of recent commits are signed; last pushed 2026-08-18. 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-19
Rank Moved
Rank dropped 16 spots (#295 → #311)
2026-08-17
Rank Moved
Rank rose 19 spots (#315 → #296)
2026-08-13
Rank Moved
Rank dropped 15 spots (#293 → #308)
Maintainer Checklist
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
78.1
Activity sub-score · out of 100
#14

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-19 05:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
727
Forks
215
Last Push
2026-08-18
yesterday
Commits (4 wk)
632
Downloads (7d)
HN mentions (30d)
Open Issues
198
Rank Change
▼16
was #295

Analysis

HVTrust Dimensions vs Observability & Evaluation

61.4 / 100 · 100.0% confidence

Traceroot Observability & Evaluation average (23 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.5 / 25
in line with avg 11.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.2 below avg 13.0
Transparency50% declared license · 50% OSSF Scorecard
14.6 / 17
2.7 above avg 11.9
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
4.8 above avg 15.1
AdoptionLog-scaled stars · package downloads
6.9 / 20
7.0 below avg 13.9

Activity Inputs

78.1 / 100
StarsRepository reach
17.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
10.9 / 20

Supply Chain Trust

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

Is Traceroot safe?

Traceroot 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 Traceroot publish package provenance?
No published build provenance is currently detected for Traceroot. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Traceroot have an OpenSSF Scorecard?
Traceroot has an OpenSSF Scorecard score of 7.2/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 Traceroot actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Traceroot use?
Traceroot ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Traceroot's commits signed?
31% of the last 100 commits to Traceroot 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
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
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
How this surface has changed

Detected changes to Traceroot'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-06-01
Activity Resumed
Activity resumed

Maintain Traceroot?

For maintainers

HVTrust scores Traceroot 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 9Listed 1Score 1HVTrust 1Grade 1Fresh 1Scorecard 1
2026-08-19
Rank Moved
Rank dropped 16 spots (#295 → #311)
2026-08-17
Rank Moved
Rank rose 19 spots (#315 → #296)
2026-08-13
Rank Moved
Rank dropped 15 spots (#293 → #308)
2026-08-12
Rank Moved
Rank rose 16 spots (#309 → #293)
2026-08-10
Rank Moved
Rank dropped 19 spots (#294 → #313)
2026-08-08
Rank Moved
Rank dropped 67 spots (#221 → #288)
2026-07-14
Rank Moved
Rank dropped 12 spots (#197 → #209)
2026-07-13
Rank Moved
Rank dropped 27 spots (#170 → #197)
2026-06-01
Scorecard Added
OSSF Scorecard: 6.9/10
2026-06-01
Activity Resumed
Activity resumed
2026-06-01
Grade Changed
Trust grade D → C
2026-06-01
Rank Moved
Rank rose 86 spots (#175 → #89)
2026-06-01
HVTrust Changed
HVTrust up 62.9pts (0.0 → 62.9)
2026-06-01
Activity Score Changed
Activity score up 77pts (0 → 77)
2026-05-31
Newly Listed
First tracked at rank #175

Embed Badge Badge guide for maintainers →

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

Other agents in Observability & Evaluation

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