Skip to main content
← Back to list
01Issue
FeatureOpenSwamp CLIPublic
AssigneesNone

Relationships

#3383 extension pull: safety analysis scans the bundle the extension runs

Opened by skunk-ape · 10/13/2026

Follow-up from swamp-club#3376.

Problem

Pull's safety analysis (src/libswamp/extensions/pull.ts, analyzeExtensionSafety over the archive's kind directories) scans only the source copy. The bundle is what runs. Archives published before #3376 can bundle local modules their source copy lacks, and any archive can bundle code from directories pull does not scan, so a clean install-time scan does not cover what executes.

Proposal

Also run the hard-error safety rules over each bundle at pull. Remap findings to modules using the per-module path comments deno bundle emits; findings outside the author's modules are reported as in a dependency. Scope stays on the extension's own code for now; scanning the full dependency tree can be re-evaluated later.

02Bog Flow
◉OPEN○TRIAGED○IN PROGRESS○SHIPPED

Open

10/13/2026, 6:56:35 PM

No activity in this phase yet.

03Sludge Pulse

Sign in to post a ripple.