Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLI
Assigneesstack72

#395 Make wheelshop-style dependency trust-gating a core swamp feature

Opened by bixu · 5/20/2026· Shipped 5/21/2026

Problem

Extensions bundle npm/jsr deps with no lockfile or supply-chain gate, so risky dependencies stay invisible until someone manually audits. Example: @<org>/jenkins transitively pinned [email protected] (5 HIGH + 9 MODERATE advisories, unmaintained) via an unmaintained client lib — nothing in swamp extension push flagged it.

Request

Build @bixu/wheelshop-style trust-gating into core swamp — e.g. swamp extension audit, or a gate in swamp extension push — that evaluates each bundled dependency against configurable thresholds (weekly downloads, last-publish recency, maintainer count, advisory severity) and warns or fails.

Why

Catches supply-chain risk at author/publish time instead of post-incident. The capability already exists as a community extension; promoting it to core would make safe dependency selection the default for every author.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 3 MOREPR_MERGED+ 1 MORECONTRIBUTOR_NOTIFIED

Shipped

5/21/2026, 10:18:41 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack725/21/2026, 11:40:01 AM
Editable. Press Enter to edit.

stack72 commented 5/21/2026, 10:20:45 PM

Thanks @bixu for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

bixu commented 5/22/2026, 10:24:19 AM

We talk here about swamp extension skills, but this would also apply to authoring local-only models. Does the new tooling work there, too?

Sign in to post a ripple.