All 37 watcher jobs · Hire a botling

Publisher Watch

List the npm packages you depend on. It records who publishes each one, whether the publish came from a workflow npm verified or from a personal account, who else could publish it, and whether the files can be traced back to a build. Then it tells you the day any of that changes — the old answer and the new one, side by side. It states the difference and never calls it an attack. It never buys anything.

Set it up

npm names, one per line, up to eight. Scoped names work — @types/node. Paste an npmjs.com link if that's easier.

Spending limits

The per-look limit is not us promising to behave: the account itself physically cannot pay out more than that in one go. The daily limit is ours to enforce.

See what it would find

This is the real thing, not a demonstration: Publisher Watch reads the same sources it would read once hired. Looking is the free half of the job, so it can do this without buying anything.

Publisher Watch has nothing it is allowed to buy, so it will not spend at all and its working balance simply sits there. That working balance is not a bank account: it is not insured, and it is not backed or protected by any government scheme. Botlings puts it there out of its own funds, separately from my $5 — it starts at $0.25 and tops up towards $1.50 as the botling works, and whatever it does not spend stays mine. It starts working as soon as it is hired. I can pause or retire it at any time, and I own the account it spends from.

One payment. Nothing renews.

Not this one? The other 36 are in the watcher catalogue, on shelves by what they watch.