updated 2026-10-03 16:08 UTC

cost-xray

Repository by tigerless-labs

See what Claude Code and Codex actually send to the API — and what each part costs.

Observability & Evaluation Python Listed MIT

Is cost-xray safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result
Provenance None
Signed commits 26%
Last push 4d ago
Compare cost-xray

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

Pick any agent to compare →
Suggest a correction

In detail: cost-xray scores 23.4/100 (Grade D), ranked #1333 of 1346 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 26% of recent commits are signed; last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How cost-xray could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships cost-xray and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run.

  1. Source Partly signed

    github.com/tigerless-labs/cost-xray, MIT, last pushed 2026-09-29. 26% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Not checked

    No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.

  3. Published packages None

    No registry package. cost-xray is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of cost-xray.

Evidence behind this score

Coverage D: 1 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks (missing)
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues cost-xray’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How cost-xray compares in Observability & Evaluation

  1. #20 TruLens 46.9 +23.5
  2. #21 SimWorld 41.6 +18.2
  3. #22 AgentBench 37.3 +13.9
  4. #23 Webarena 36.3 +12.9
  5. #24 cost-xray 23.4 this agent

Bars show each HVTrust score; the tick marks cost-xray’s 23.4.

Where the 23.4 comes from

HVTrust dimensions vs the Observability & Evaluation average

23.4 / 100 · 50.0% confidence

cost-xray Observability & Evaluation average (24 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.3 / 25
10.4 below avg 11.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.4 below avg 13.2
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.7 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
13.6 / 20
1.3 below avg 14.9
AdoptionLog-scaled stars · package downloads
8.6 / 20
4.9 below avg 13.5

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-10-01
Newly Listed
First tracked at rank #1333
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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for cost-xray View Observability & Evaluation Report missing data
69.6
Activity sub-score · out of 100
#24
In Observability & Evaluation

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

Signals refreshed 2026-10-03 16:08 UTC · Repo last pushed 4 days ago

Rank Trend

2026-10-01 2026-10-03

Activity & Reach

Stars
3.8k
Forks
307
Last Push
2026-09-29
4 days ago
Commits (4 wk)
8?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
9
Rank Change
=
was #1333

Analysis

Activity Inputs

69.6 / 100
StarsRepository reach
21.5 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
11.6 / 20

Common questions about cost-xray

Public trust evidence for cost-xray 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 cost-xray publish package provenance?
No published build provenance is currently detected for cost-xray. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does cost-xray have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for cost-xray. 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 cost-xray actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does cost-xray use?
cost-xray ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are cost-xray's commits signed?
26% of the last 100 commits to cost-xray 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
cost-xray appears to expose MCP server capabilities.
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
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

Maintain cost-xray?

For maintainers

HVTrust scores cost-xray 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1
2026-10-01
Newly Listed
First tracked at rank #1333
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Observability & Evaluation

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON