Is Machines safe and trustworthy?

tashan scores Machines on public evidence — it is currently abandoned, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, it runs a script at install time, its declared dependencies reach: database. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Machines?

Don't. This capability has been discontinued by its author or publisher and is not scored or recommended. If you are already running it, `npx tashan-cli doctor` will flag it and name what to move to.

‹ The Index

Machines

npm

Machine fleet management CLI + MCP for developers

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Design — see all ranked ›

Discontinued — do not install. The author's own notice: “Machine fleet management CLI + MCP for developers” It stays listed so anyone already running it can find this page, and so npx tashan-cli doctor can warn about it. It is not scored and does not appear in any ranking.

Looking for a replacement? npx tashan-cli doctor is free and tells you everything above about your whole config. tashan Pro names the replacement — which one, and how it measures. $6/mo.

Adoption: 13k/wk
Freshness: 94.0
Health: abandoned
License: Apache-2.0

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 0.2.39 — this package, not its dependency tree

Runs a script at install timecodenode postinstall.js

Connects to databasesfrom declared dependencies

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-09-12 @hasna/machines was marked deprecated on npm The publisher is telling installers to stop using it.
2026-09-12 the command @hasna/machines runs at install time changed The code that executes on your machine is not the code you last approved.
2026-08-25 @hasna/machines published 0.2.36, was 0.2.35 A new release is available.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 4 changes to Machines in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

npm ↗ · source ↗ · pkg:@hasna/machines

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-12 · scorer s5 · how · something wrong here?