IWE
Website
Markdown knowledge graph — LSP for your editor, CLI + MCP memory for your AI agents
Is IWE safe? Promising trust profile, but some evidence still deserves review.
Compare IWE
How does it stack up against its Memory & Knowledge neighbours?
Pick any agent to compare →In detail: IWE scores 65.9/100 (Grade B), ranked #446 of 1346 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; 58% of recent commits are signed; no published advisory affects its latest release (iwe); last pushed 2026-10-02. Every point is earned from checkable signals — never paid placement. How scoring works →
How IWE could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 4.8 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Contributors 0 +8.8 → 74.7 B · #13 of 46
- Sign every commit58% signed today +2.1 → 68.0 B · #26 of 46
Chain of custody
Scanners check what the code says. This traces who ships IWE and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install.
-
Source Partly signed
github.com/iwe-org/iwe, Apache-2.0, last pushed 2026-10-02. 58% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.8/10 (scanned Sep 30, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 0Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases 0Token-Permissions 0Vulnerabilities 8 -
Published packages Linked, not attested
- crates.io iwe Source link points back to this repo Attestation not checked on this registry
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: iwe 0.25.0. No published advisory affects it (OSV, checked 2026-10-03).
Changes to this chain
- 2026-09-23 License classification changed from unlicensed to open
- 2026-08-29 OSSF Scorecard: 4.8/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues IWE’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How IWE compares in Memory & Knowledge
- #25 Qdrant 68.1 +2.2
- #26 Pond 67.6 +1.7
- #27 IWE 65.9 this agent
- #28 Beads 65.2 −0.7
- #29 WeKnora 65.1 −0.8
Bars show each HVTrust score; the tick marks IWE’s 65.9.
Where the 65.9 comes from
HVTrust dimensions vs the Memory & Knowledge average
65.9 / 100 · 100.0% confidenceIWE Memory & Knowledge average (46 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
69.4 / 100Common questions about IWE
Does IWE publish package provenance?
Does IWE have an OpenSSF Scorecard?
Is IWE actively maintained?
What license does IWE use?
Are IWE's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to IWE'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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/iwe)
<a href="https://hvtracker.net/agents/iwe"><img src="https://hvtracker.net/badge/iwe.svg" alt="HVTrust"></a>
Other agents in Memory & Knowledge
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.4 · Raw JSON