Ktx has an HVTrust score of 16.6/100 (Grade D), ranked #136 of 148 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Ktx?

Ktx scores 16.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.5k GitHub stars and is categorized under Agent Skills.

Ktx

Kaelio/ktx

ktx is an executable context layer for data and analytics agents 🐙 Allow Claude Code, Codex, or other AI agents to query

Agent Skills TypeScript Grade D Listed Apache-2.0

16.6/100

Rank #136 of 148

Compare Ktx

How does it stack up against its Agent Skills 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 D · 1/5 signals

Last push

2026-07-19 · 24d ago

Recent change

New

Is Ktx safe? Ktx scores 16.6/100 (Grade D), ranked #136 of 148 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; 62% of recent commits are signed; last pushed 2026-07-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#134 Super Agent Party — 16.9 (D) → #135 Baoyu Skills — 16.7 (D) → #137 Claude Ads — 15.5 (D) → #138 Brooks Lint — 15.5 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-11

Newly Listed

First tracked at rank #136

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.

Compare with another agent Get email alerts for Ktx View Agent Skills Report missing data

50.2

Activity sub-score · out of 100

#136

In Agent Skills

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 →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

1.5k

Forks

Last Push

2026-07-19

24 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #136

Analysis

HVTrust Dimensions vs Agent Skills

16.6 / 100 · 40.0% confidence

Ktx Agent Skills average (148 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

3.1 / 25

in line with avg 2.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.5 below avg 11.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.5

Maintenance60% last-push freshness · 40% commit activity

10.4 / 20

4.7 below avg 15.1

AdoptionLog-scaled stars · package downloads

7.6 / 20

1.6 below avg 9.2

Activity Inputs

50.2 / 100

StarsRepository reach

19.1 / 30

FreshnessLast push recency

21.7 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

9.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

62%

of last 100 commits verified

Is Ktx safe?

Public trust evidence for Ktx 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 Ktx publish package provenance?

No published build provenance is currently detected for Ktx. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Ktx have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for Ktx. 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 Ktx actively maintained?

Maintained. Last push was 24 days ago.

What license does Ktx use?

Ktx ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Ktx's commits signed?

62% of the last 100 commits to Ktx 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

high confidence

Implemented

Ktx appears to expose MCP server capabilities.

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

high confidence

2 tags

Broad capability areas detected.

code
database

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Ktx?

For maintainers

HVTrust scores Ktx 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

2026-08-11

Newly Listed

First tracked at rank #136

GitHub → PyPI: ktx-workspace

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/ktx.svg)](https://hvtracker.net/agents/ktx)
            
HTML:
            <a href="https://hvtracker.net/agents/ktx"><img src="https://hvtracker.net/badge/ktx.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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