IWE

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

Memory & Knowledge Rust Listed Apache-2.0

Is IWE safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.5 / 10
Provenance None
Signed commits 49%
Last push 2d ago
Advisories None known
Compare IWE

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

Pick any agent to compare →
Suggest a correction

In detail: IWE scores 65.3/100 (Grade B), ranked #526 of 1387 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.5/10; 49% of recent commits are signed; no published advisory affects its latest release (iwe); last pushed 2026-11-15. 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.

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. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/iwe-org/iwe, Apache-2.0, last pushed 2026-11-15. 49% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.5/10 (scanned Nov 1, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection1
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 1
    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 5
  3. 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.

  4. What you install today No known advisories

    Latest release checked: iwe 0.33.0. No published advisory affects it (OSV, checked 2026-11-17).

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

  1. #28 Utopia 66.9 +1.6
  2. #29 Quivr 65.4 +0.1
  3. #30 IWE 65.3 this agent
  4. #31 Chroma 64.9 −0.4
  5. #32 Beads 64.6 −0.7

Bars show each HVTrust score; the tick marks IWE’s 65.3.

Where the 65.3 comes from

HVTrust dimensions vs the Memory & Knowledge average

65.3 / 100 · 100.0% confidence

IWE Memory & Knowledge average (52 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.1 / 25
3.9 below avg 12.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.8 below avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
0.7 below avg 13.0
Maintenance60% last-push freshness · 40% commit activity
17.6 / 20
in line with avg 17.3
AdoptionLog-scaled stars · package downloads
10.5 / 20
2.6 below avg 13.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-29
Rank Moved
Rank rose 10 spots (#497 → #487)
2026-10-27
Rank Moved
Rank dropped 10 spots (#486 → #496)
2026-10-21
Rank Moved
Rank rose 10 spots (#504 → #494)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.5/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.
71.6
Activity sub-score · out of 100
#30

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-11-17 20:09 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-11-17

Activity & Reach

Stars
1.8k
Forks
94
Last Push
2026-11-15
2 days ago
Commits (4 wk)
27
Downloads (7d)
101
crates.io
HN mentions (30d)
—
Open Issues
1
Rank Change
▼8
was #518

Analysis

Activity Inputs

71.6 / 100
StarsRepository reach
19.6 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
18.1 / 25
CommunityFork signal
9.2 / 20

Common questions about IWE

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.5/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 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?
49% 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
How this surface has changed

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.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

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
Rank 26HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1MCP 1License 1
2026-10-29
Rank Moved
Rank rose 10 spots (#497 → #487)
2026-10-27
Rank Moved
Rank dropped 10 spots (#486 → #496)
2026-10-21
Rank Moved
Rank rose 10 spots (#504 → #494)
2026-10-18
Rank Moved
Rank dropped 17 spots (#473 → #490)
2026-10-16
Rank Moved
Rank rose 13 spots (#486 → #473)
2026-10-15
Rank Moved
Rank rose 14 spots (#500 → #486)
2026-10-12
Rank Moved
Rank dropped 12 spots (#485 → #497)
2026-10-09
Rank Moved
Rank dropped 39 spots (#444 → #483)
2026-10-08
Rank Moved
Rank rose 13 spots (#457 → #444)
2026-10-02
Rank Moved
Rank rose 15 spots (#458 → #443)
2026-09-26
Rank Moved
Rank rose 16 spots (#444 → #428)
2026-09-24
Rank Moved
Rank dropped 10 spots (#431 → #441)
2026-09-23
License Changed
License classification changed from unlicensed to open
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 270 spots (#701 → #431)
2026-09-23
HVTrust Changed
HVTrust up 35.3pts (30.9 → 66.2)
2026-09-22
Newly Listed
First tracked at rank #701
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank rose 10 spots (#422 → #412)
2026-09-11
Rank Moved
Rank dropped 15 spots (#404 → #419)
2026-09-08
Rank Moved
Rank dropped 12 spots (#391 → #403)
2026-09-07
Rank Moved
Rank dropped 32 spots (#359 → #391)
2026-09-05
Rank Moved
Rank dropped 61 spots (#294 → #355)
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)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 65.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.4 · Raw JSON