Skip to the content

Getting started

What slowship is

slowship is a careful reader for everything your project brings aboard. It reads the code of your packages, your coding agent’s skills and MCP servers, and your own build, without running any of it, and tells you which ones do more than they say.

The morning report: the verdict on the left, the project drawn as a ship in harbour on the right, and four counts of what it read below
The morning report after one watch. The verdict is on the left. Your project is the ship, with one container for each thing aboard.

#The idea in one example

Say you install a package called tidy-dates. Its description says: “Formats dates the way people say them.” That’s its promise.

slowship opens its code and lists what the code can actually do. Here it finds three things:

  1. It formats dates. The description says so. That’s fine.
  2. It reads your npm login file. The description never mentions it.
  3. It sends data to a server. The description doesn’t mention this either.

Reading a login file right next to a network call is one of the few combinations slowship treats as serious. So the verdict is held in port, and the report shows you the exact lines that did it.

That’s the whole job: does this do what it says it does? Most things do. slowship stays quiet about those and only speaks up, with evidence, when something doesn’t.

#What you get in the morning

Every watch ends in one of three verdicts:

VerdictWhat it meansWhat to do
Held in portSomething does more than it says, and the proof is a combination found in its code.Look at it before you ship.
Ready after a glanceNothing serious. A few single facts the descriptions don’t mention.Spend a few seconds on each, then clear them.
Cleared to sailEverything aboard does what it says, as far as its code shows.Ship it.

#What makes it different

#Where to go next

Or try the live demo: the real report page, replaying one recorded night.

Suggest a change to this page

Esc