pickfit

BrowseInfra & DevOps tools

restic

Command-line backup program that stores encrypted, deduplicated snapshots on local disks, SFTP, REST servers or cloud storage.

Use it

Before you install: known vulnerabilities

pickfit found 1 known high or critical vulnerability in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.

  • go:github.com/go-jose/go-jose/v4 v4.1.4 Go JOSE: DoS when parsing JWKs that contain RSA keys (GHSA-mgcc-cww5-fp2q, high, fixed in 4.1.6)

Linux x86_64

You need first

  • Runtimes: go>=1.26.10 (only for building from source)
  1. Download the official v0.19.1 linux_amd64 release binary, unpack it into ~/.local/bin/restic and make it executable

    mkdir -p ~/.local/bin && curl -fsSL -o /tmp/restic.bz2 https://github.com/restic/restic/releases/download/v0.19.1/restic_0.19.1_linux_amd64.bz2 && bunzip2 -c /tmp/restic.bz2 > ~/.local/bin/restic && chmod +x ~/.local/bin/restic

Check that it works

restic version

The output should contain “restic 0.19.1 compiled with”.

First thing to try

restic version

Run restic version to confirm it works, then create a repository with restic init --repo <repo> --password-file <password-file>.

What it does

  • Create encrypted backup snapshots
    How to use it
    1. Create a repository with restic init --repo <repo> --password-file <password-file>.
    2. Back up a folder with restic --repo <repo> --password-file <password-file> backup <folder>.
    3. Verify the repository with restic --repo <repo> --password-file <password-file> check.
    Tested
  • Store duplicate data only once
    How to use it
    1. Run restic --repo <repo> --password-file <password-file> backup <folder>; identical file contents are stored only once.
    Tested
  • Restore files or mount snapshots
    How to use it
    1. Restore a folder from the newest snapshot with restic --repo <repo> --password-file <password-file> restore latest:<folder> --target <restore-folder>.
    Tested
  • Store backups on many cloud storage services
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • back up a directory to a local repository
  • back up to an SFTP server over SSH
  • store backups in Amazon S3 or S3-compatible storage
  • browse files from previous snapshots via FUSE mount

How pickfit tested it

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

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version restic 0.19.1 compiled with go1.26.4 on linux/amd64

Differences the test machine hit

  • README: Build from source with git clone + go run build.go, or install with apk/pacman/apt-get/dnf/mise
    In the test: No Go toolchain or root here, and mise isn't installed, so I used the official prebuilt binary from GitHub releases (restic_0.19.1_linux_amd64.bz2), which the install guide also offers
  • README: restic init / backup prompt for a password
    In the test: I passed --password-file so the commands run without anyone typing (stdin is closed)
  • README: use `restic restore` to restore files
    In the test: Restoring 'latest' into a target recreated the /tmp parent directory, and lchown on it failed in this box (exit 1, though all the file data was written). Restoring the subtree with 'latest:/tmp/rdata' avoided this.

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.