cost-xray

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? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.2 / 10
Provenance None
Signed commits 47%
Last push 5d 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 61.8/100 (Grade C), ranked #656 of 1387 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 5.2/10; 47% of recent commits are signed; last pushed 2026-11-12. 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.

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. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

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

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.2/10 (scanned Nov 15, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 5
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 6
  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

  • 2026-10-17 OSSF Scorecard: 4.3/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • 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.

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. #15 Holmesgpt 67.2 +5.4
  2. #16 Helicone 63.8 +2.0
  3. #17 cost-xray 61.8 this agent
  4. #18 Traceroot 61.4 −0.4
  5. #19 Reverify 61.4 −0.4

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

Where the 61.8 comes from

HVTrust dimensions vs the Observability & Evaluation average

61.8 / 100 · 100.0% confidence

cost-xray Observability & Evaluation average (28 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.8 / 25
2.8 below avg 11.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.3 below avg 13.1
Transparency50% declared license · 50% OSSF Scorecard
12.9 / 17
0.6 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
18.3 / 20
3.8 above avg 14.5
AdoptionLog-scaled stars · package downloads
9.0 / 20
4.1 below avg 13.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-13
Rank Moved
Rank dropped 12 spots (#634 → #646)
2026-11-12
Rank Moved
Rank rose 10 spots (#644 → #634)
2026-11-11
Rank Moved
Rank rose 11 spots (#655 → #644)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.2/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
79.5
Activity sub-score · out of 100
#17

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-11-17 20:09 UTC · Repo last pushed 5 days ago

Rank Trend

2026-10-01 2026-11-17

Activity & Reach

Stars
5.8k
Forks
377
Last Push
2026-11-12
5 days ago
Commits (4 wk)
44
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
4
Rank Change
▲7
was #663

Analysis

Activity Inputs

79.5 / 100
StarsRepository reach
22.6 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
20.6 / 25
CommunityFork signal
12.0 / 20

Common questions about cost-xray

cost-xray 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 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?
cost-xray has an OpenSSF Scorecard score of 5.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 cost-xray actively maintained?
Actively maintained. The repository was pushed to within the last 5 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?
47% 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.

Reputation Timeline

Signal history
Rank 14Listed 1Score 1HVTrust 1Grade 1Scorecard 1
2026-11-13
Rank Moved
Rank dropped 12 spots (#634 → #646)
2026-11-12
Rank Moved
Rank rose 10 spots (#644 → #634)
2026-11-11
Rank Moved
Rank rose 11 spots (#655 → #644)
2026-11-10
Rank Moved
Rank dropped 10 spots (#645 → #655)
2026-11-08
Rank Moved
Rank dropped 34 spots (#614 → #648)
2026-11-05
Rank Moved
Rank rose 22 spots (#636 → #614)
2026-11-02
Rank Moved
Rank rose 15 spots (#650 → #635)
2026-10-30
Rank Moved
Rank rose 34 spots (#678 → #644)
2026-10-29
Rank Moved
Rank dropped 10 spots (#668 → #678)
2026-10-28
Rank Moved
Rank rose 43 spots (#711 → #668)
2026-10-23
Rank Moved
Rank rose 43 spots (#746 → #703)
2026-10-19
Rank Moved
Rank dropped 12 spots (#734 → #746)
2026-10-17
Scorecard Added
OSSF Scorecard: 4.3/10
2026-10-17
Grade Changed
Trust grade D → C
2026-10-17
Rank Moved
Rank rose 635 spots (#1362 → #727)
2026-10-17
HVTrust Changed
HVTrust up 32.6pts (25.7 → 58.3)
2026-10-14
Activity Score Changed
Activity score up 7pts (66 → 73)
2026-10-09
Rank Moved
Rank dropped 18 spots (#1333 → #1351)
2026-10-01
Newly Listed
First tracked at rank #1333

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 61.8 Grade C
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON