Is WeKnora safe to use?

WeKnora has an HVTrust score of 62.2/100 (Grade C), ranked #294 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for WeKnora?

WeKnora scores 62.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 19.7k GitHub stars and is categorized under Memory & Knowledge.

WeKnora

Tencent/WeKnora

Open-source LLM knowledge platform: turn raw documents into a queryable RAG, an autonomous reasoning agent, and a self-m

Memory & Knowledge Go Grade C Listed NOASSERTION

62.2/100

Rank #294 of 1283

Compare WeKnora

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-12 · 0d ago

Recent change

Rank

Is WeKnora safe? WeKnora scores 62.2/100 (Grade C), ranked #294 of 1283 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.6/10; 2% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#21 agentmemory — 66.9 (B) → #22 Zvec — 64.5 (C) → #24 memU — 61.5 (C) → #25 Beads — 61.2 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 81 spots (#208 → #289)

2026-07-14

Rank Moved

Rank dropped 14 spots (#223 → #237)

2026-07-13

Rank Moved

Rank dropped 29 spots (#194 → #223)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for WeKnora View Memory & Knowledge Report missing data

91.9

Activity sub-score · out of 100

#23

In Memory & Knowledge

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

2026-08-11 2026-08-12

Activity & Reach

Stars

19.7k

Forks

2.8k

Last Push

2026-08-12

today

Commits (4 wk)

383

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

334

Rank Change

▲1

was #295

Analysis

HVTrust Dimensions vs Memory & Knowledge

62.2 / 100 · 100.0% confidence

WeKnora Memory & Knowledge average (42 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.1 / 25

3.0 below avg 10.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.4 below avg 12.2

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

0.8 above avg 12.5

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

2.3 above avg 17.7

AdoptionLog-scaled stars · package downloads

10.3 / 20

3.2 below avg 13.6

Activity Inputs

91.9 / 100

StarsRepository reach

25.8 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

16.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.6 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 9

CII-Best-Practices 0

Code-Review 7

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 9

Maintained 10

Packaging 10

Pinned-Dependencies 1

SAST 0

Security-Policy 4

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is WeKnora safe?

WeKnora 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 WeKnora publish package provenance?

No published build provenance is currently detected for WeKnora. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does WeKnora have an OpenSSF Scorecard?

WeKnora has an OpenSSF Scorecard score of 5.6/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 WeKnora actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does WeKnora use?

WeKnora ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are WeKnora's commits signed?

2% of the last 100 commits to WeKnora 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.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

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

high confidence

Implemented

WeKnora appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

browser

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-08

Rank Moved

Rank dropped 81 spots (#208 → #289)

2026-07-14

Rank Moved

Rank dropped 14 spots (#223 → #237)

2026-07-13

Rank Moved

Rank dropped 29 spots (#194 → #223)

2026-06-24

Newly Listed

First tracked at rank #178

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/weknora.svg)](https://hvtracker.net/agents/weknora)
            
HTML:
            <a href="https://hvtracker.net/agents/weknora"><img src="https://hvtracker.net/badge/weknora.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
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