Husk

Name: Husk
Author: husk-security

by husk-securityversion 0.1.2i★ –iRuns on your computer

Registry nameio.github.husk-security/husk

Install

Overview

Description from the maker (original English)

Local-first defensive scanner for vulnerable dependencies, leaked secrets, and risky agent configs

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "husk": {
      "command": "npx",
      "args": [
        "-y",
        "husk-sec",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add husk -- npx -y husk-sec mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "husk": {
      "command": "npx",
      "args": [
        "-y",
        "husk-sec",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "husk": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "husk-sec",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account husk-security, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32678 servers in this category
Published to the registry more recently than 41% of the other 32678 servers in this category
Basic checks equal to or better than 100% of the other 32678 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Husk safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Rust on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Starreel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Starreel

by starreel

Turn a script into a finished, downloadable short-drama episode — via MCP or REST.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

A local-first security scanner for developers. One binary, no account.

Install · Quickstart · Usage · Commands · How it works

husk scans your machine for compromised packages, leaked secrets, risky install scripts, and unsafe AI/MCP configuration, then shows you what to fix. It runs locally: no login, no account, no file ever leaves your machine. An online scan sends only package names, versions, and CVE ids to public advisory databases (OSV.dev, npm, PyPI, GitHub, CISA KEV / FIRST EPSS); --offline makes zero network calls.

Pre-1.0 software without an independent audit. Interfaces can change

between releases. Bug reports and questions are welcome in

Issues.

Install

husk runs on Linux and macOS. On Windows, run it inside WSL, where it installs and behaves exactly as it does on Linux. There is no native Windows build.

Download the latest signed release, verify its checksum, and install it:

curl -fsSL https://husk-security.dev/install.sh | sh

It installs to ~/.local/bin, overridable with HUSK_INSTALL_DIR or --install-dir. If that directory is not already on your PATH, it asks before adding it to your shell's startup file and names the exact file it would change. Decline, or run it without a terminal, and it prints the one command that adds it instead. --no-modify-path never writes to a startup file at all.

Prefer not to pipe into a shell? Download install.sh, read it, then run it. Every release is cosign-signed and SLSA-attested; the installer verifies the SHA-256 checksum (and the signature too, when cosign is on your PATH). See verifying a release.

Other install sources

| Source | Command |

| --- | --- |

| cargo | cargo install husk-sec |

| cargo-binstall | cargo binstall husk-sec |

| npm | npm install -g husk-sec |

Nix

Run it without installing anything:

`sh

nix run github:husk-security/husk -- scan

`

The flake exposes two packages: husk (the default, with the localhost web

UI) and husk-tui (the same binary without it, so it needs no Node

toolchain).

For persistent use, add the flake as an input and put the package in your

configuration. NixOS:

`nix

{

inputs.husk.url = "github:husk-security/husk";

inputs.husk.inputs.nixpkgs.follows = "nixpkgs";

outputs = { nixpkgs, husk, ... }: {

nixosConfigurations.myhost = nixpkgs.lib.nixosSystem {

system = "x86_64-linux";

modules = [

{ environment.systemPackages = [ husk.packages.x86_64-linux.husk ]; }

];

};

}

`

Home Manager, with the same input:

`nix

home.packages = [ husk.packages.x86_64-linux.husk ];

`

If you would rather put it on PATH imperatively than declare it,

nix profile install github:husk-security/husk also works.

Quickstart

husk            # print help (no subcommand does nothing else)

husk scan # one-shot scan of the current directory, plain terminal summary husk web # serve the local web UI and open it in your browser husk tui # browse the latest scan in the terminal UI

husk with no subcommand prints help and exits, like git or cargo. The entry points are husk scan (scan and print the report), husk web (the local web UI, opened in your browser), and husk tui (the terminal UI).

Usage

A few of the commands you'll actually run day to day. The full list (every subcommand and flag) is in the command reference.

Scan a directory and print the findings report:

$ husk scan --offline .

packages: 286 findings: 36 critical: 5 high: 16 medium: 15 low: 0 info: 0

critical risky-agent-config AI agent is allowed unrestricted shell access .claude/settings.local.json:4 high lifecycle-script Dangerous npm postinstall script package.json:6 high risky-agent-config MCP config contains hardcoded secret .mcp.json:7 ...

Vet one package before you install it (a live OSV.dev lookup):

$ husk check lodash@4.17.20

!! vulnerable npm lodash@4.17.20 advisory GHSA-35jh-r3h4-6jhm via OSV.dev Command Injection in lodash Install a fixed version instead, or avoid the dependency until one is available.

The version can be an @version suffix (split on the last @, so @scope/pkg@1.2.3 works) or separate arguments: husk check npm lodash 4.17.20. A bare name (husk check lodash) assumes npm and checks malware advisories only.

Protect normal and lockfile installs with the tracked Safe Chain task in the Guide. Husk recommends the free, MIT-licensed third-party tool instead of shipping a weaker package-manager wrapper:

Review Aikido Safe Chain

Commit a project policy (block/allow packages, suppress triaged findings, set the CI threshold); the .husk/ directory is meant to be committed:

$ husk init

Created ./.husk/policy.toml husk scan and husk ci in this project now read this policy.

$ husk approve npm:lodash # allow a package; recorded in policy + ledger

Plan safe fixes (dry-run by default; --apply writes them, with backups):

husk fix                          # show the plan, change nothing

husk fix --apply # write the auto-safe fixes

Gate a build in CI, JSON on stdout, non-zero exit at or above the threshold:

husk ci                           # exit 1 on high+ findings (see JSON output below)

Environment

husk reads a few environment variables:

Variable	Effect
`HUSK_HOME`	State directory (ledger, daemon state, credentials); default `~/.husk`.
`HUSK_CACHE_DIR`	Cache directory (reports, scan index); default `~/.cache/husk`.
`HUSK_PAGER`, `PAGER`	Pager for long reports (default `less`); an empty value or `cat` disables paging.
`NO_COLOR`	Disable ANSI colors in CLI output.
`HUSK_TOKEN`	Bearer-token override for cloud commands (CI or one-off use).

Command reference

One binary, many subcommands. Run husk --help for the full flags of any of them.

`husk scan`: Scan now and print the findings report
`husk status`: Print the last scan's report without rescanning
`husk tui`: Open the interactive terminal UI on the latest scan
`husk web`: Serve the local web UI on the latest scan
`husk check`: Look up one package's malware/vulnerability verdict
`husk ci`: Scan and gate a build; exit 1 at/above the threshold
`husk fix`: Plan fixes from the latest scan; write them with --apply
`husk init`: Create a committed .husk/policy.toml project policy
`husk approve`: Record an allow/block/suppress decision in the policy
`husk policy`: Show the active project policy and its counts
`husk ledger`: Show or verify the personal trust ledger
`husk daemon`: Scan on an interval; report findings new since last run
`husk login`: Sign in to a husk account (coming soon)
`husk logout`: Delete the credentials stored on this machine
`husk account`: Show the signed-in account and machine link
`husk sync`: Upload the last scan's inventory for retroactive alerts
`husk alerts`: List this account's retroactive alerts
`husk telemetry`: Manage opt-in anonymous telemetry (off by default)
`husk feedback`: Send feedback to the husk developers
`husk mcp`: Run the MCP server, or register it with an AI agent

JSON output

Several commands emit the full scan report as JSON: husk scan --json, husk status --json, husk tui --json, and husk ci (always JSON). The shape is identical everywhere; it is the report the local cache stores and every UI renders. It is plain JSON on stdout: never paged, never colored, safe to pipe straight into jq.

Field	Type	Meaning
`api_version`	number	Report-shape version (currently `4`). Bumped when the shape changes; check it before parsing deeply.
`generated_at`	string (RFC 3339)	When the scan finished. Reports older than 24 hours are considered stale by the UIs.
`roots`	string[]	The directories that were scanned.
`context`	object	System context: user, OS/arch, distro, kernel, git identity, detected package managers and dev configs.
`packages`	object[]	The package inventory: `{ecosystem, name, version, manifest_path, line}` per discovered coordinate.
`projects`	object[]	Discovered projects (the unit of attention); findings join to these via `Finding.project_id`.
`summary`	object	The security headline (counts and framing used by the UIs).
`findings`	object[]	Open findings. Each has `id`, `title`, `severity` (`critical`/`high`/`medium`/`low`/`info`), `category`, `source`, `path`, `line`, `summary`, `evidence` (pre-redacted), `recommendation`, `references`, `cves`, plus optional `package`, `project_id`, `rule_id`, `confidence`, `priority`, `exploit` (CISA KEV / EPSS), and `fixed_version`.
`ignored`	object[]	Findings silenced by project policy or ledger decisions, kept out of `findings`, stats, and scoring.
`controls`	object[]	Results from registered guide controls: status, local evidence, and related finding ids.
`remediations`	object[]	Typed remediation proposals owned by controls; includes execution class, severity, operation, and related finding ids.
`guidance`	object	The assessed Markdown guide: baseline/recommendation items, scan priority, review decisions, and handled percentage.
`providers`	object[]	Per intel source: `{name, ok, checked_packages, findings, message}`. `ok: false` means coverage was incomplete.
`benchmarks`	object[]	Per-stage timing: `{stage, elapsed_ms, files_checked, bytes_scanned, packages_checked, findings, workers, detail}`.
`stats`	object	Totals: `{packages, findings, critical, high, medium, low, info}`.
`delta`	object?	What changed since the previous cached scan of the same roots: `{previous_at, previous_score, score, new_count, unchanged_count, resolved_count, resolved}`. Absent on a first scan.

husk scan --json | jq -r '.findings[].id'                 # every finding id, worst first

test "$(husk status --json | jq .stats.critical)" -eq 0 # fail a script on any critical husk ci | jq '.providers[] | select(.ok | not)' # which intel sources had problems

How it works

Local-first. Scans read files and parse them statically; husk never executes what it scans. Results and state stay on your machine; an online scan sends only package coordinates and CVE ids to public advisory databases.
Package coverage. Discovery is a pluggable registry spanning ~68 package ecosystems (language managers, OS/distro databases, AI/agent/editor surfaces, CI/IaC/containers, and CycloneDX/SPDX SBOMs), see src/scan/targets/.
Exploit-aware. CISA KEV and FIRST EPSS enrichment sorts actively-exploited CVEs to the top instead of dumping an undifferentiated CVE list.
State that compounds. A commi

Only the beginning is shown; read the rest in the repo

Husk

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Starreel

README from the maker

Install

Quickstart

Usage

Environment

Command reference

JSON output

How it works