Is txtai safe?
txtai scores 63.2/100 (Grade C), ranked #135 of 328 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.7/10;
2% of recent commits are signed;
last pushed 2026-07-02. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
63.2/100 · Grade C
Strongest Signal
Maintenance
16.7/20
Weakest Signal
Safety / Integrity
6.0/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-06-24
Rank Moved
Rank dropped 11 spots (#146 → #157)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 4.7/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
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 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 refreshed2026-07-11 05:00 UTC·Repo last pushed 9 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
12.7k
Forks
843
Last Push
2026-07-02
9 days ago
Commits (4 wk)
20
Downloads (7d)
8,876
pypi
HN mentions (30d)
0
Open Issues
10
Rank Change
=
was #135
Analysis
HVTrust Dimensions
63.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
6.0 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.5 / 17
MaintenanceFreshness and commits
16.7 / 20
AdoptionStars and downloads
15.1 / 20
Activity Inputs
78.6 / 100
StarsRepository reach
24.6 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
16.5 / 25
CommunityFork signal
13.6 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.7 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
2%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection0
CI-Tests10
CII-Best-Practices0
Code-Review0
Contributors3
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities10
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.7/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?
Maintained. Last push was 9 days ago.
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.
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.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
3 tags
Broad capability areas detected.
code
database
search
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
How this surface has changed
Detected changes to txtai's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Detected MCP server support changed: none → declared
Maintain txtai?
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.
