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
50.2/100
Rank #313 of 468
Compare LLM Wiki Agent

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 · 3d ago
Recent change
No recent signal change

Is LLM Wiki Agent safe? LLM Wiki Agent scores 50.2/100 (Grade C), ranked #313 of 468 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

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
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.
72.1
Activity sub-score · out of 100
#29

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 →

Signals refreshed 2026-08-06 05:00 UTC · Repo last pushed 3 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
3.3k
Forks
386
Last Push
2026-08-03
3 days ago
Commits (4 wk)
13
Downloads (7d)
HN mentions (30d)
Open Issues
2
Rank Change
=
was #313

Analysis

HVTrust Dimensions vs Memory & Knowledge

50.2 / 100 · 100.0% confidence

LLM Wiki Agent Memory & Knowledge average (37 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.2 / 25
4.3 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.6 below avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
11.2 / 17
1.4 below avg 12.6
Maintenance60% last-push freshness · 40% commit activity
16.4 / 20
1.3 below avg 17.7
AdoptionLog-scaled stars · package downloads
8.5 / 20
5.7 below avg 14.2

Activity Inputs

72.1 / 100
StarsRepository reach
21.1 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
14.3 / 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 5, 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 3 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
3 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • code
  • search
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 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.

Reputation Timeline

Signal history
Rank 5Grade 4Listed 1HVTrust 1Scorecard 1
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.2 Grade C
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