IWE has an HVTrust score of 39.7/100 (Grade D), ranked #644 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for IWE?

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

IWE

iwe-org/iwe

Markdown knowledge graph — LSP for your editor, CLI + MCP memory for your AI agents

Memory & Knowledge Rust Grade D Listed Apache-2.0

39.7/100

Rank #644 of 1308

Compare IWE

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-15 · 2d ago

Recent change

New

Is IWE safe? IWE scores 39.7/100 (Grade D), ranked #644 of 1308 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 60% of recent commits are signed; last pushed 2026-08-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#38 AnythingLLM — 43.1 (D) → #39 Honcho — 40.0 (D) → #41 Pond — 38.2 (D) → #42 Titen — 35.6 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-16

Newly Listed

First tracked at rank #646

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

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

70.7

Activity sub-score · out of 100

#40

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 D 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-16 2026-08-17

Activity & Reach

Stars

1.5k

Forks

Last Push

2026-08-15

2 days ago

Commits (4 wk)

Downloads (7d)

134

crates.io

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #646

Analysis

HVTrust Dimensions vs Memory & Knowledge

39.7 / 100 · 67.0% confidence

IWE Memory & Knowledge average (44 agents)

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

3.0 / 25

6.9 below avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.3 below avg 12.1

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.8 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

17.7 / 20

in line with avg 17.7

AdoptionLog-scaled stars · package downloads

10.5 / 20

3.1 below avg 13.6

Activity Inputs

70.7 / 100

StarsRepository reach

19.1 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

18.2 / 25

CommunityFork signal

8.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

60%

of last 100 commits verified

Is IWE safe?

Public trust evidence for IWE 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 IWE publish package provenance?

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

Does IWE have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for IWE. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is IWE actively maintained?

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

What license does IWE use?

IWE ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are IWE's commits signed?

60% of the last 100 commits to IWE 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

medium confidence

Implemented

IWE appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain IWE?

For maintainers

HVTrust scores IWE 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-16

Newly Listed

First tracked at rank #646

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · crates.io (downloads)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON