updated 2026-08-19 05:02 UTC

txtai

neuml/txtai

💡 All-in-one AI framework for semantic search, LLM orchestration and language model workflows

Memory & Knowledge Python Grade B Listed Apache-2.0
68.3/100
Rank #171 of 1308
Compare txtai

How does it stack up against its Memory & Knowledge 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 A · 4/5 signals
Last push
2026-08-18 · 1d ago
Recent change
Rank

Is txtai safe? txtai scores 68.3/100 (Grade B), ranked #171 of 1308 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.8/10; 2% 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 Memory & Knowledge

#17 Code-Graph-RAG — 68.6 (B) → #18 Vellum Assistant — 68.3 (B) → #20 Khoj — 68.1 (B) → #21 agentmemory — 67.4 (B) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-13
Rank Moved
Rank dropped 17 spots (#147 → #164)
2026-08-08
Rank Moved
Rank dropped 18 spots (#132 → #150)
2026-07-21
Grade Changed
Trust grade C → B
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/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.
Compare with another agent Get email alerts for txtai View Memory & Knowledge Report missing data
87.5
Activity sub-score · out of 100
#19
In Memory & Knowledge

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

Signals refreshed 2026-08-19 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
12.9k
Forks
876
Last Push
2026-08-18
yesterday
Commits (4 wk)
85
Downloads (7d)
8,876
pypi
HN mentions (30d)
0
Open Issues
9
Rank Change
▼8
was #163

Analysis

HVTrust Dimensions vs Memory & Knowledge

68.3 / 100 · 100.0% confidence

txtai Memory & Knowledge average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.1 / 25
3.8 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
in line with avg 12.4
Maintenance60% last-push freshness · 40% commit activity
19.7 / 20
2.0 above avg 17.7
AdoptionLog-scaled stars · package downloads
15.1 / 20
1.5 above avg 13.6

Activity Inputs

87.5 / 100
StarsRepository reach
24.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
24.1 / 25
CommunityFork signal
13.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.8 / 10
OpenSSF Scorecard · scanned Aug 18, 2026
Signed Commits
2%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 4
CII-Best-Practices 0
Code-Review 4
Contributors 3
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 10

Is txtai safe?

txtai 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 txtai publish package provenance?
No published build provenance is currently detected for txtai. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does txtai have an OpenSSF Scorecard?
txtai has an OpenSSF Scorecard score of 4.8/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 txtai actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does txtai use?
txtai ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are txtai's commits signed?
2% of the last 100 commits to txtai 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 txtai?

For maintainers

HVTrust scores txtai 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
Rank 5HVTrust 2Listed 1Score 1Grade 1
2026-08-13
Rank Moved
Rank dropped 17 spots (#147 → #164)
2026-08-08
Rank Moved
Rank dropped 18 spots (#132 → #150)
2026-07-21
Grade Changed
Trust grade C → B
2026-07-21
Rank Moved
Rank rose 12 spots (#161 → #149)
2026-06-24
Rank Moved
Rank dropped 11 spots (#146 → #157)
2026-06-01
Rank Moved
Rank dropped 13 spots (#83 → #96)
2026-05-29
HVTrust Changed
HVTrust up 9.7pts (49.0 → 58.7)
2026-05-28
Activity Score Changed
Activity score up 19pts (62 → 82)
2026-05-27
HVTrust Changed
HVTrust up 7.9pts (46.8 → 54.7)
2026-05-25
Newly Listed
First tracked at rank #90
GitHub → PyPI: txtai

Embed Badge Badge guide for maintainers →

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

Other agents in Memory & Knowledge

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