A draughtsman's section of a canal lock: a barge of stacked shipping containers waits in the low chamber below the closed gate.

Écluse

A supply-chain policy proxy for package registries.

Écluse is a proxy you put in front of public package registries to protect the builds that install from them. Point your CI and developer tooling at Écluse instead of at a public registry. Écluse fetches from that registry on their behalf and decides which versions a build may install. The npm registry is the first one supported, and any client that speaks its protocol works, such as npm, pnpm, yarn, or bun. The name is French for a canal lock: the controlled passage every dependency clears before it reaches your build.

A new public version waits in a quarantine, seven days by default, before a build can install it. Most malicious publishes are found and pulled within days, so the wait alone sidesteps them, with no attempt to detect malice. With an advisory database synced, a version that an advisory names as the exact fix for a vulnerability skips the wait, so the quarantine never delays a security patch. Everything else is deny by default and opt-in by name.

If you run a private registry, Écluse reads it first and passes your own packages through untouched. Any https registry that speaks the ecosystem's protocol serves in that role. Écluse can also mirror each admitted public version into a registry you nominate, so a mirrored version survives a public outage or yank. For an AWS CodeArtifact mirror target Écluse mints the short-lived write token itself, and any other host takes a static token you supply. Écluse hosts no packages itself.