Quarantine Package

Quarantine Package

Run an npm package in a sealed sandbox on Vultr and see what it tried to do, before you install it.

Every run ends in a public receipt page you can link to.

How it works

  1. Download

    Fetched from the registry with install scripts off.

  2. Model predicts

    Vultr Serverless Inference predicts behaviour and writes a test harness.

  3. Sandbox run

    Installed and run in a disposable hardened sandbox, traced. Network ends at a sinkhole.

  4. Verdict + receipt

    Fixed rules decide. The receipt is public.

One-click demos

Each demo runs the full pipeline on a known package or a fixture from the repo.

express@4.21.2

A popular benign web framework.

Expected install

fastify@5.12.4

Real dependency from the author's payments project.

Expected install

Install script that downloads

repo fixture, never published

A legitimate-looking script that fetches a binary.

Expected review

Hostile package

repo fixture, never published

Writes to /etc, reaches for docker.sock and credentials, POSTs data out.

Expected do-not-install

Fork bomb

repo fixture, never published

Spawns processes without limit; the pids limit stops it in seconds.

Expected do-not-install

Infinite loop

repo fixture, never published

Never exits; the 60 s wall clock kills it.

Expected do-not-install

Example receipts

install/r/d6fbf70332review/r/d5af19b228do-not-install/r/8b42cfb93e