updated 2026-09-04 23:12 UTC

IWE

iwe-org/iwe

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

Memory & Knowledge Rust Grade B Listed Apache-2.0
66.3/100
Rank #294 of 1320
Compare IWE

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 B · 3/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Rank +8

Is IWE safe? IWE scores 66.3/100 (Grade B), ranked #294 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.8/10; 60% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#20 txtai — 69.6 (B) → #21 Code-Graph-RAG — 68.3 (B) → #23 Pond — 66.1 (B) → #24 Khoj — 65.1 (B) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-03
Rank Moved
Rank dropped 16 spots (#275 → #291)
2026-09-01
Rank Moved
Rank dropped 16 spots (#260 → #276)
2026-08-31
Rank Moved
Rank dropped 25 spots (#235 → #260)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/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.
Compare with another agent Get email alerts for IWE View Memory & Knowledge Report missing data
70.0
Activity sub-score · out of 100
#22
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 B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 23:12 UTC · Repo last pushed today

Rank Trend

2026-08-16 2026-09-04

Activity & Reach

Stars
1.6k
Forks
74
Last Push
2026-09-04
today
Commits (4 wk)
22
Downloads (7d)
126
crates.io
HN mentions (30d)
—
Open Issues
0
Rank Change
▼3
was #291

Analysis

HVTrust Dimensions vs Memory & Knowledge

66.3 / 100 · 100.0% confidence

IWE Memory & Knowledge average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.0 / 25
2.4 below avg 11.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.6 below avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
in line with avg 12.9
Maintenance60% last-push freshness · 40% commit activity
17.4 / 20
in line with avg 17.6
AdoptionLog-scaled stars · package downloads
10.5 / 20
2.8 below avg 13.3

Activity Inputs

70.0 / 100
StarsRepository reach
19.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
17.0 / 25
CommunityFork signal
8.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.8 / 10
OpenSSF Scorecard · scanned Aug 29, 2026
Signed Commits
60%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 8

Is IWE safe?

IWE 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 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?
IWE has an OpenSSF Scorecard score of 4.8/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 IWE actively maintained?
Actively maintained. The repository was pushed to within the last 1 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
Rank 8Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-03
Rank Moved
Rank dropped 16 spots (#275 → #291)
2026-09-01
Rank Moved
Rank dropped 16 spots (#260 → #276)
2026-08-31
Rank Moved
Rank dropped 25 spots (#235 → #260)
2026-08-30
Rank Moved
Rank rose 15 spots (#250 → #235)
2026-08-29
Scorecard Added
OSSF Scorecard: 4.8/10
2026-08-29
Grade Changed
Trust grade D → B
2026-08-29
Rank Moved
Rank rose 549 spots (#799 → #250)
2026-08-29
HVTrust Changed
HVTrust up 26.9pts (39.3 → 66.2)
2026-08-28
Rank Moved
Rank dropped 25 spots (#774 → #799)
2026-08-27
Rank Moved
Rank dropped 22 spots (#752 → #774)
2026-08-26
Rank Moved
Rank dropped 104 spots (#648 → #752)
2026-08-16
Newly Listed
First tracked at rank #646
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 66.3 Grade B
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON