Khoj
Website
Your AI second brain. Self-hostable. Get answers from the web or your docs. Build custom agents, schedule automations, do deep research. Turn any online or local LLM into your personal, autonomous AI (gpt, claude, gemini, llama, qwen, mistral). Get started - free.
Is Khoj safe? Promising trust profile, but some evidence still deserves review.
Compare Khoj
How does it stack up against its Memory & Knowledge neighbours?
Pick any agent to compare →In detail: Khoj scores 61.3/100 (Grade C), ranked #618 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.4/10; 22% of recent commits are signed; last pushed 2026-08-02. Every point is earned from checkable signals — never paid placement. How scoring works →
How Khoj 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.
- Raise the OSSF Scorecard from 3.4 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Dependency-Update-Tool 0 +11.8 → 73.1 B · #18 of 49
- Sign every commit22% signed today +4.0 → 65.3 B · #30 of 49
Chain of custody
Scanners check what the code says. This traces who ships Khoj and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/khoj-ai/khoj, AGPL-3.0, last pushed 2026-08-02. 22% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.4/10 (scanned Sep 24, 2026, refresh pending). The checks that decide who can get a change released:
- Code Review3
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 9Branch-Protection 0CI-Tests 8CII-Best-Practices 0Code-Review 3Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 5Packaging 10Pinned-Dependencies 0SAST 1Security-Policy 0Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages Partly attested
- PyPI khoj Source link isn't a GitHub repo Build provenance attested
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Khoj.
Evidence behind this score
Coverage A: 4 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Khoj’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 Khoj compares in Memory & Knowledge
- #32 Zvec 63.7 +2.4
- #33 AnythingLLM 61.7 +0.4
- #34 Khoj 61.3 this agent
- #35 PrivateGPT 58.3 −3.0
- #36 memU 56.6 −4.7
Bars show each HVTrust score; the tick marks Khoj’s 61.3.
Where the 61.3 comes from
HVTrust dimensions vs the Memory & Knowledge average
61.3 / 100 · 100.0% confidenceKhoj Memory & Knowledge average (49 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
58.9 / 100Common questions about Khoj
Does Khoj publish package provenance?
Does Khoj have an OpenSSF Scorecard?
Is Khoj actively maintained?
What license does Khoj use?
Are Khoj's commits signed?
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
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 →
- code
- database
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Khoj?
For maintainers
HVTrust scores Khoj 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/khoj)
<a href="https://hvtracker.net/agents/khoj"><img src="https://hvtracker.net/badge/khoj.svg" alt="HVTrust"></a>
Other agents in Memory & Knowledge
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.4 · Raw JSON