Is LLM Wiki Agent safe to use?

LLM Wiki Agent has an HVTrust score of 51.1/100 (Grade C), ranked #428 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for LLM Wiki Agent?

LLM Wiki Agent scores 51.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.3k GitHub stars and is categorized under Memory & Knowledge.

LLM Wiki Agent

SamurAIGPT/llm-wiki-agent

A personal knowledge base that builds and maintains itself. Drop in sources — Claude (or Codex/Gemini) reads them, extra

Memory & Knowledge Python Grade C Listed MIT

51.1/100

Rank #428 of 1204

Compare LLM Wiki Agent

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-03 · 6d ago

Recent change

Rank +3

Is LLM Wiki Agent safe? LLM Wiki Agent scores 51.1/100 (Grade C), ranked #428 of 1204 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 3.2/10; 45% of recent commits are signed; last pushed 2026-08-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#28 OpenViking — 55.7 (C) → #29 Letta — 55.4 (C) → #31 LightMem — 50.2 (C) → #32 Memvid — 49.2 (D) →

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 107 spots (#314 → #421)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini, OpenAI

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.2/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 LLM Wiki Agent View Memory & Knowledge Report missing data

70.8

Activity sub-score · out of 100

#30

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 →

Activity & Reach

Stars

3.3k

Forks

389

Last Push

2026-08-03

6 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼7

was #421

Analysis

HVTrust Dimensions vs Memory & Knowledge

51.1 / 100 · 100.0% confidence

LLM Wiki Agent Memory & Knowledge average (38 agents)

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

6.2 / 25

4.4 below avg 10.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.5 below avg 12.3

Transparency50% declared license · 50% OSSF Scorecard

11.2 / 17

1.5 below avg 12.7

Maintenance60% last-push freshness · 40% commit activity

15.9 / 20

1.6 below avg 17.5

AdoptionLog-scaled stars · package downloads

8.5 / 20

5.6 below avg 14.1

Activity Inputs

70.8 / 100

StarsRepository reach

21.1 / 30

FreshnessLast push recency

24.2 / 25

ActivityRecent commits

13.5 / 25

CommunityFork signal

12.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.2 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

45%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 3

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is LLM Wiki Agent safe?

Public trust evidence for LLM Wiki Agent is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does LLM Wiki Agent publish package provenance?

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

Does LLM Wiki Agent have an OpenSSF Scorecard?

LLM Wiki Agent has an OpenSSF Scorecard score of 3.2/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 LLM Wiki Agent actively maintained?

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

What license does LLM Wiki Agent use?

LLM Wiki Agent ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are LLM Wiki Agent's commits signed?

44% of the last 100 commits to LLM Wiki Agent 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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

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

How this surface has changed

Detected changes to LLM Wiki Agent'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-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini, OpenAI

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)

Maintain LLM Wiki Agent?

For maintainers

HVTrust scores LLM Wiki Agent 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 107 spots (#314 → #421)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini, OpenAI

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)

2026-07-27

Grade Changed

Trust grade D → C

2026-07-21

Grade Changed

Trust grade C → D

2026-07-15

Rank Moved

Rank dropped 23 spots (#276 → #299)

2026-07-14

Rank Moved

Rank dropped 14 spots (#262 → #276)

2026-07-13

Rank Moved

Rank dropped 31 spots (#231 → #262)

2026-07-11

Grade Changed

Trust grade D → C

2026-06-24

Scorecard Added

OSSF Scorecard: 3.4/10

2026-06-24

Grade Changed

Trust grade D → C

2026-06-24

Rank Moved

Rank rose 68 spots (#290 → #222)

2026-06-24

HVTrust Changed

HVTrust up 29.8pts (22.8 → 52.6)

2026-06-23

Rank Moved

Rank dropped 11 spots (#279 → #290)

2026-06-21

Newly Listed

First tracked at rank #276

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/llm-wiki-agent.svg)](https://hvtracker.net/agents/llm-wiki-agent)
            
HTML:
            <a href="https://hvtracker.net/agents/llm-wiki-agent"><img src="https://hvtracker.net/badge/llm-wiki-agent.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.2 · Raw JSON