WeKnora
Open-source LLM knowledge platform: turn raw documents into a queryable RAG, an autonomous reasoning agent, and a self-maintaining Wiki.
Is WeKnora safe? Promising trust profile, but some evidence still deserves review.
Compare WeKnora
How does it stack up against its Memory & Knowledge neighbours?
Pick any agent to compare →In detail: WeKnora scores 64.8/100 (Grade C), ranked #480 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.4/10; 53% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How WeKnora compares in Memory & Knowledge
- #26 Pond 67.8 +3.0
- #27 IWE 66.2 +1.4
- #28 WeKnora 64.8 this agent
- #29 Beads 64.7 −0.1
- #30 Zvec 64.3 −0.5
Bars show each HVTrust score; the tick marks WeKnora’s 64.8.
Where the 64.8 comes from
HVTrust dimensions vs the Memory & Knowledge average
64.8 / 100 · 100.0% confidenceWeKnora Memory & Knowledge average (44 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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
93.7 / 100Supply Chain Trust
Common questions about WeKnora
Does WeKnora publish package provenance?
Does WeKnora have an OpenSSF Scorecard?
Is WeKnora actively maintained?
What license does WeKnora use?
Are WeKnora'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 →
- browser
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain WeKnora?
For maintainers
HVTrust scores WeKnora 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/weknora)
<a href="https://hvtracker.net/agents/weknora"><img src="https://hvtracker.net/badge/weknora.svg" alt="HVTrust"></a>
Other agents in Memory & Knowledge
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON