Item detail
github.com

neuml/txtai

RepoRadar surfaced neuml/txtai — a developer tool — into the Radar section, where it sits at Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.8 out of 10.

Score8.3
Popularity8.5
Risklow
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum8.0
Maturity6.7
Open-source/build8.4
Evidence7.2
Workflow potential9.8
Setup ease8.8

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for AI application teams, semantic-search engineers, and AI agent builders who need an Apache-2.0-licensed, open-source all-in-one AI framework for semantic search, LLM orchestration, embeddings, and language-model workflows that ships as a Python library, an API server, and a vector+graph+relational backend stack, so they can run a single OSS toolkit that covers retrieval, RAG, and LLM

Who should use it

AI application teams who need an Apache-2.0-licensed, open-source all-in-one AI framework for semantic search, LLM orchestration, embeddings, and language-model workflows semantic-search engineers who want a vector+graph+relational backend stack from a single OSS toolkit AI agent builders who need a single Python library that covers retrieval, RAG, and LLM orchestration without stitching together half a dozen separate packages open-source contributors who want an Apache-2.0-licensed alternative to stitched-together LangChain + FAISS + sentence-transformers stacks

Who should skip it

Skip neuml/txtai if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.

About this signal

neuml/txtai is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-21; the source record was last checked on 2026-06-21. The current verdict is 'try now' with a Gold tier and easy setup difficulty. Across RepoRadar's eight signals, neuml/txtai is strongest on workflow potential (9.8) and practical usefulness (9.0) and weakest on maturity (6.7) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The neuml/txtai record combines a 8.3/10 composite score with separate popularity (8.5), risk (low), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

It is an Apache-2.0-licensed all-in-one AI framework that runs as a Python library or a local API server, so review which corpora the index is allowed to ingest, scope which queries the system answers, confirm that API endpoints are auth-protected before exposing them outside localhost, and gate any production rollout behind a retrieval-quality review pass.

Evidence links
Closest alternatives / related signals
semantic-search rag llm-orchestration embeddings vector-database graph-database all-in-one open-source
Verification record

What RepoRadar actually verified

Tested in a bounded workflow

Bounded representative workflow retained by RepoRadar verification harness. Last checked 2026-07-13T10:36:32.646116Z.

partial · cohort-20260712-txtai-import

Tester
RepoRadar automated local verification harness
Started
2026-07-13T03:23:10.254791Z
Completed
2026-07-13T03:23:32.059201Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
0 minute(s)
Evidence scope
Bounded setup or capability check
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Executed bounded check: Install and import txtai in an isolated Python environment.
  • Captured the complete sanitized stdout, stderr, exit status, and 21.80-second wall time.
Observed results
  • Command exited 0 after 21.80 seconds.
  • Expected marker 'CHECK_OK' was observed in retained output.
Observed strengths
  • txtai==9.11.0 installed and imported successfully in the isolated Python environment, emitting the expected version marker.
Friction
  • The command emitted stderr; warnings or errors are preserved in the retained log for review.
Limitations
  • No embeddings model, index, database, API server, or model inference was used.
  • This bounded cohort check is not a production benchmark or a claim of real user-workflow adoption.

Pricing assessment: No paid plan or metered provider usage was exercised; package or licensing, hosting, and provider costs remain workflow-dependent.

Privacy assessment: No repository content, user data, or provider prompt was transmitted; broader product data handling was not assessed by this bounded run.

Open retained test log →

passed · cohort-20260712-txtai-keyword-retrieval-workflow

Tester
RepoRadar automated local verification harness
Started
2026-07-13T10:36:09.759483Z
Completed
2026-07-13T10:36:32.646116Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded representative workflow
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Created 1 synthetic fixture file(s) inside the disposable work directory; retained hashes prove the exact inputs.
  • Configured txtai for content-backed keyword retrieval and indexed three synthetic operational runbooks.
  • Searched for checkout rollback, asserted the rollback record ranked first, and exported the ranked result and corpus count.
  • Executed bounded check: Index three synthetic runbooks and retrieve the checkout rollback record through txtai's local keyword index.
  • Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 22.89-second wall time.
Observed results
  • Command exited 0 after 22.89 seconds.
  • txtai indexed all three documents and returned the rollback runbook as the top keyword result.
  • Expected marker 'CHECK_OK top=rollback count=3 returned=1' was observed in retained output.
  • Validated result.json: 3 required marker(s) present and 0 excluded marker(s) absent; size and SHA-256 are retained.
Observed strengths
  • The same Embeddings interface can provide a fully local keyword index when an embedding model is intentionally unavailable.
Friction
  • Installing txtai includes substantial optional ML dependencies even though this bounded workflow uses only its keyword path.
  • Setup or runtime emitted 11 stderr line(s); the complete warnings/errors are preserved in the retained log.
Limitations
  • The keyword-only configuration validates indexing and BM25-style retrieval without embeddings; it does not test semantic models, hybrid search, persistence, pipelines, or an API server.
  • This credential-free disposable workflow does not establish production scale, model quality, reliability under sustained use, or team adoption.

Pricing assessment: The keyword index ran locally with no embedding model download, API request, hosted database, or paid service.

Privacy assessment: Only synthetic runbooks were tokenized and searched in process; no model hub, telemetry endpoint, or remote index received content.

Open retained test log →

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

44 dated snapshots retained from 2026-06-21 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.3 current · +0.0 net
Repository momentum9.3 current · +1.3 net
GitHub stars (observed)12,887 current · +166 net
GitHub stars12,887 exact observation
Versionv9.12.0
Last release2026-07-30T19:43:23Z
Maintenanceactive
Current risklow
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.39.312,887lowtry nowactive
2026-08-128.39.612,880lowtry nowactive
2026-08-118.39.612,861lowtry nowactive
2026-08-108.39.312,828lowtry nowactive
2026-08-098.39.312,820lowtry nowactive
2026-08-088.39.312,813lowtry nowactive
2026-08-078.39.312,777lowtry nowactive
2026-08-068.38.0Not recordedlowtry nownot recorded
2026-08-058.38.0Not recordedlowtry nownot recorded
2026-08-048.39.312,777lowtry nowactive
2026-08-038.39.312,777lowtry nowactive
2026-08-028.39.312,774lowtry nowactive

Why the record changed

stars changed

Stars changed: 12880 → 12887.

stars changed

Stars changed: 12861 → 12880.

stars changed

Stars changed: 12828 → 12861.

stars changed

Stars changed: 12820 → 12828.

stars changed

Stars changed: 12813 → 12820.

stars changed

Stars changed: 12777 → 12813.

stars changed

Stars changed: 12774 → 12777.

stars changed

Stars changed: 12771 → 12774.

stars changed

Source-observed stars changed: 12770 → 12771. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 12761 → 12765.

stars changed

Source-observed stars changed: 12760 → 12761. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 12728 → 12760.