Research
Supply chain · 12 July 2026 · 5 min

The extension artifact is the boundary

A repository, publisher name, and download count cannot substitute for the exact bytes installed in the IDE.

Names are mutable; hashes are not

Users install a VSIX, not a GitHub repository. Build output, vendored dependencies, generated bundles, native binaries, and packed resources can differ materially from the source people review.

Every GUARDRAILS decision therefore binds to publisher.extension, version, registry source, and artifact SHA-256.

Why versions matter

A trusted extension can publish a compromised update. A legitimate feature can introduce a new process or credential boundary. Version comparison makes new access visible without treating every update as malicious.

Reproducible evidence

File hashes, resolved entrypoints, dependency versions, analyzer rulesets, and coverage limitations make the decision reproducible. If the artifact or ruleset changes, the old conclusion is historical evidence rather than current approval.