SMSnippet MarketThe Trust Layer for Code
Marketplace/ollama

Incident repricing

ollama / ollama

The moment exploit probability rises, the market punishes the repo and the agent verdict hardens to block.

Seeded laneseeded_lane
42trust

Operator Scenarios

Switch the room from narrative to repricing.

Reset board

Live now

Exploit odds spike on Ollama

Injects a critical incident into a fast-growth repo and flips the agent verdict from review to block.

Available

LangChain funds trust aggressively

Shows how increasing the security budget and audit coverage can move a high-growth repo into the allow range.

Available

Express recovers maintainership

Demonstrates that operational discipline can rehabilitate a legacy dependency's trust profile.

Narrative

New risk, immediate consequence

Fast-moving runtime under active incident pressure. Trust collapsed until coverage improves.

View GitHub repo

Signal composition

Trust breakdown

Security Budget

41
Demo Seeded
Weight 26%Confidence 74%

Stake Depth

40
Demo Seeded
Weight 22%Confidence 74%

Audit Coverage

31
Demo Seeded
Weight 20%Confidence 74%

Maintainer Responsiveness

48
Derived
Weight 12%Confidence 90%

Incident Pressure

74
Derived
Weight 12%Confidence 90%

Adoption Confidence

94
Demo Seeded
Weight 8%Confidence 74%

Agent Verdict

Hold the dependency

Trust and security signals are too weak for autonomous use without stronger audit coverage or market backing.

Threshold 74

Provenance

Every signal carries a disclosure label.

Demo-seeded volatility storyDemo Seeded

Real repo with seeded scenario controls for live repricing.

Source link

Recent events

Trust moves when the repo moves.

Compare this repo

  1. Critical exploit report surfaced

    Mar 13, 2026, 3:28 PM

    Operator-triggered incident injects a new critical signal and drains confidence across the stack.

    Demo Seeded-15.9

  2. Agent platform integrations accelerated

    Mar 12, 2026, 12:05 PM

    Usage climbed faster than the repo's visible trust budget.

    Derived+0.0