Is Khoj safe?
Khoj scores 70.0/100 (Grade B), ranked #86 of 328 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.7/10;
16% of recent commits are signed;
last pushed 2026-06-24. 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.
70.0/100 · Grade B
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
12.9/25
What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-06-24
Grade Changed
Trust grade C → B
2026-06-24
Rank Moved
Rank rose 72 spots (#131 → #59)
2026-06-24
HVTrust Changed
HVTrust up 9.2pts (64.4 → 73.6)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 3.7/10. Tighten the weakest checks to improve public safety evidence.
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 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 refreshed2026-07-11 05:00 UTC·Repo last pushed 17 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
35.6k
Forks
2.3k
Last Push
2026-06-24
17 days ago
Commits (4 wk)
10
Downloads (7d)
5,365
pypi
HN mentions (30d)
14
Open Issues
96
Rank Change
▼3
was #83
Analysis
HVTrust Dimensions
70.0 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.9 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
11.6 / 17
MaintenanceFreshness and commits
15.0 / 20
AdoptionStars and downloads
15.9 / 20
Activity Inputs
78.7 / 100
StarsRepository reach
27.3 / 30
FreshnessLast push recency
22.6 / 25
ActivityRecent commits
13.0 / 25
CommunityFork signal
15.6 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
3.7 / 10
OpenSSF Scorecard · scanned Jul 11, 2026
Signed Commits
16%
of last 100 commits verified
Binary-Artifacts9
Branch-Protection0
CI-Tests8
CII-Best-Practices0
Code-Review3
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies0
SAST1
Security-Policy0
Signed-Releases0
Token-Permissions0
Vulnerabilities0
Is Khoj safe?
Khoj 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 Khoj publish package provenance?
Yes. Khoj's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Khoj have an OpenSSF Scorecard?
Khoj has an OpenSSF Scorecard score of 3.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 Khoj actively maintained?
Maintained. Last push was 17 days ago.
What license does Khoj use?
Khoj ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Khoj's commits signed?
16% of the last 100 commits to Khoj 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
None detected
No MCP server signal detected.
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
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
How this surface has changed
Detected changes to Khoj'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.
2026-06-05
Provider Added
Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, E2B, Google Gemini, OpenAI, Postgres
2026-05-24
Provenance Added
Package provenance attestation detected
Maintain Khoj?
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.
