pickfit

BrowseDeveloper CLIs

ark

CLI to manage Ark genomic enclaves, their data, apps, and firmware.

Tested on macOS and Linux

Use it

macOS arm64

  1. install ark via brew stable

    brew install dark-bio/tap/ark-cli

Check that it works

ark --version 2>&1

The output should contain “ark 0.5.0”.

First thing to try

ark devices 2>&1

Run ark devices to find connected Ark hardware and running emulators.

Linux x86_64

  1. download installer script only

    curl -fsSL https://github.com/dark-bio/cli/releases/latest/download/ark-installer.sh -o /tmp/ark-installer.sh
  2. run installer script

    sh /tmp/ark-installer.sh

Check that it works

ark --version

The output should contain “ark 0.5.0”.

First thing to try

ark devices

Run ark devices to find connected Ark hardware and running emulators.

What it does

  • Run apps and print their reports
    Not tested
  • Upload variant calls to the Ark
    Not tested
  • Download public data onto the Ark
    Not tested
  • List dataset slots and their state
    Not tested

How far pickfit got

macOS arm64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • find connected Ark hardware and running emulators
  • show Ark serial, firmware, pairing and lock status
  • upload variant calls file to the Ark
  • run a WASM app on the Ark and save its report

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 0.5.0

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.5.0

Differences the test machine hit

  • README: curl installer script | sh installs ark
    In the test: installer fetches compiled binary ark-0.5.0-linux-amd64 and LICENSES.txt at run time; binary cannot be read as text before running
  • README: On Linux, your user needs access to the Ark's USB device once via sudo tee udev rule
    In the test: skipped udev rule (requires sudo/root, not available); ark devices still runs and reports no-device with USB warning

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.