TruLens

Evaluation and Tracking for LLM Experiments and AI Agents

Observability & Evaluation Python Grade D Listed MIT
44.3/100
Rank #552 of 1308
Compare TruLens

How does it stack up against its Observability & Evaluation neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-14 · 5d ago
Recent change
Rank +1

Is TruLens safe? TruLens scores 44.3/100 (Grade D), ranked #552 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 100% of recent commits are signed; last pushed 2026-08-14. 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
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-13
Rank Moved
Rank dropped 12 spots (#525 → #537)
2026-08-12
Rank Moved
Rank rose 14 spots (#539 → #525)
2026-08-10
Rank Moved
Rank dropped 14 spots (#526 → #540)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
80.6
Activity sub-score · out of 100
#19

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-19 06:02 UTC · Repo last pushed 5 days ago

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
3.5k
Forks
325
Last Push
2026-08-14
5 days ago
Commits (4 wk)
72?
Downloads (7d)
12,963
pypi
HN mentions (30d)
22
Open Issues
22
Rank Change
▼8
was #544

Analysis

HVTrust Dimensions vs Observability & Evaluation

44.3 / 100 · 75.0% confidence

TruLens Observability & Evaluation average (23 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
6.0 below 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
8.5 / 17
3.4 below avg 11.9
Maintenance60% last-push freshness · 40% commit activity
15.4 / 20
in line with avg 15.1
AdoptionLog-scaled stars · package downloads
14.0 / 20
in line with avg 13.9

Activity Inputs

80.6 / 100
StarsRepository reach
21.3 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
23.2 / 25
CommunityFork signal
11.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
Not available
Signed Commits
100%
of last 100 commits verified

Is TruLens safe?

Public trust evidence for TruLens is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does TruLens publish package provenance?
No published build provenance is currently detected for TruLens. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does TruLens have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for TruLens. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is TruLens actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does TruLens use?
TruLens ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are TruLens's commits signed?
100% of the last 100 commits to TruLens 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
low confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
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

Maintain TruLens?

For maintainers

HVTrust scores TruLens 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 16Score 5Listed 1HVTrust 1
2026-08-13
Rank Moved
Rank dropped 12 spots (#525 → #537)
2026-08-12
Rank Moved
Rank rose 14 spots (#539 → #525)
2026-08-10
Rank Moved
Rank dropped 14 spots (#526 → #540)
2026-08-08
Rank Moved
Rank dropped 153 spots (#371 → #524)
2026-07-20
Activity Score Changed
Activity score up 7pts (66 → 73)
2026-07-15
Rank Moved
Rank dropped 25 spots (#336 → #361)
2026-07-14
Rank Moved
Rank dropped 17 spots (#319 → #336)
2026-07-13
Rank Moved
Rank dropped 36 spots (#283 → #319)
2026-06-24
Rank Moved
Rank dropped 35 spots (#254 → #289)
2026-06-23
Rank Moved
Rank dropped 22 spots (#232 → #254)
2026-06-22
Rank Moved
Rank dropped 10 spots (#222 → #232)
2026-06-21
Rank Moved
Rank dropped 14 spots (#208 → #222)
2026-06-18
Rank Moved
Rank dropped 13 spots (#186 → #199)
2026-06-10
Rank Moved
Rank dropped 12 spots (#173 → #185)
2026-06-10
Activity Score Changed
Activity score down 6pts (75 → 69)
2026-06-08
Activity Score Changed
Activity score up 6pts (69 → 75)
2026-06-07
Activity Score Changed
Activity score down 6pts (75 → 69)
2026-06-02
Rank Moved
Rank dropped 10 spots (#150 → #160)
2026-06-01
Rank Moved
Rank dropped 15 spots (#135 → #150)
2026-05-29
Rank Moved
Rank dropped 20 spots (#114 → #134)
2026-05-28
Activity Score Changed
Activity score up 19pts (57 → 76)
2026-05-27
HVTrust Changed
HVTrust up 25.5pts (33.2 → 58.7)
2026-05-25
Newly Listed
First tracked at rank #122

Embed Badge Badge guide for maintainers →

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

Other agents in Observability & Evaluation

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