croc is a free command-line tool that sends files and folders from one computer to another. Run croc send with a file name and it prints a short code phrase; type croc and that phrase on the other computer, accept, and the files arrive, encrypted end to end with a key made from the phrase. Neither side needs an account, an open port or the same network, and an interrupted transfer picks up where it stopped.
It earns its place because it works the same on Windows, macOS, Linux and in a browser, so you can move a big file from your laptop to a friend's PC, a server or a phone without email limits or a cloud drive. When the two computers cannot connect directly, the data goes through a relay: by default a public pool at getcroc.com run by the author, which only ever sees encrypted data, or your own with croc relay. Newer extras include encrypted links that wait for the other person (croc store) and terminal sharing (croc ssh).
croc is MIT-licensed and written in Go by Zack Scholl (schollz), who started it in 2017. It has about 41,000 stars and around 175 contributors. Version 11.6.5 came out on 7 November 2026.
- Repository: github.com/schollz/croc
- Licence: MIT (MIT License)
- Language: Go. Stars: 41K. Forks: 1,662. Last push: Nov 20, 2026.
- Scan: safe, Nov 21, 2026, commit 440ed73
Who it is for
Anyone who moves files between their own computers, developers copying files to and from servers, people sending large files to friends, and family IT helpers. It runs on Windows, macOS and Linux from a terminal, and in a browser at getcroc.com with no install.
Getting started
1. Install on macOS or Linux with Homebrew
brew install croc2. Or on Windows, with Scoop
scoop install croc3. Or on Linux, the official installer, which asks for sudo to write to /usr/local/bin
curl https://getcroc.com | bash4. Send a file or folder; croc prints a code phrase to give the other person
croc send photo.jpg5. On the other computer, type croc and the code phrase it printed, then accept
croc your-code-phraseHomebrew and Scoop install croc without touching your shell files. The getcroc.com installer checks each download against the release's SHA-256 checksums and puts croc and croc-update in /usr/local/bin, using sudo or doas, or in a folder you pick with -p. Files you receive are saved in the current folder once you accept them. Our scan covers the source code, not the prebuilt binaries.
Safety scan
We cloned schollz/croc at commit 440ed73 on Nov 21, 2026 and ran the checks described on the GitHub Tools page: credential patterns, decode-and-execute code, install-time scripts, committed binaries, risky CI workflows, every host the code talks to, known vulnerabilities in pinned dependencies, and project hygiene. A person read every hit. This is what we found.
- 0 secret hits and no committed binaries across 517 files and about 104,000 lines: Go for the program, TypeScript for the getcroc.com web app.
- 4 pattern hits, all the text curl https://getcroc.com | bash stored as data: once in src/webassets/assets_test.go, a test that the site serves the installer, and three times in blog posts in web/src/blog-posts.ts. None of them runs anything.
- The installer is src/install/default.txt, served at getcroc.com; we fetched it on 21 November 2026 and it matched. It downloads the release for your system from GitHub, verifies it against the release's SHA-256 checksum file, and installs croc and croc-update into /usr/local/bin with sudo or doas, or into any folder you name with -p. It does not edit shell files. scripts/install-benchmark-prereqs.sh, flagged for sudo and shell edits, only prepares the developers' speed tests.
- 0 advisories across the 114 Go modules in go.mod, which is the program. The 10 advisories (4 high, 6 moderate) are all in web/package-lock.json and all in the website's test tools: undici, pulled in by jsdom, and Vitest's mocker. Neither ships in croc or the site.
- By default a transfer that cannot go direct uses the public relays 1.getcroc.com to 4.getcroc.com, run by the author; the code phrase sets up the encryption, so the relay passes on data it cannot read, and --relay or CROC_RELAY points croc at your own. At most once a day a send or receive checks api.github.com for a newer release; CROC_NO_UPDATE_CHECK=1 turns that off. The relay can count sessions in Umami analytics if its operator sets that up, and the getcroc.com site carries Google ads and Umami analytics, left off its stored-file pages. 8 workflows, no pull_request_target, all 7 third-party actions pinned to commits, and Windows builds are code-signed. A security policy and Dependabot are present; no CodeQL. OpenSSF Scorecard gives it 5.3 out of 10.
What the scanner counted
| Check | Result |
|---|---|
| Secrets | None found. |
| Suspicious code | 4 pattern hits found and read; every one is listed under the raw findings. |
| Install-time code | 1 installer script (one edits your shell profile; one can call sudo) |
| Committed binaries | None. |
| CI workflows | 8 workflows. None use pull_request_target. 0 of 7 third-party actions pinned to a tag rather than a commit. |
| Network hosts | 40 distinct hosts referenced from source; most often github.com, getcroc.com, example.test, api.github.com. No URLs to bare IP addresses. |
| Known vulnerabilities | 10 advisories across 314 pinned packages: 0 critical, 4 high, 6 moderate, 0 low. go.mod: 114 packages, 0 advisories; web/package-lock.json: 200 packages, 10 advisories. |
| Project hygiene | Has security policy, automated dependency updates, licence file. Missing CodeQL, contributing guide. |
| OpenSSF Scorecard | 5.3 out of 10, as of Oct 26, 2026. |
The raw findings
Every hit the scanner wrote out, with a link to the exact line at the scanned commit. Secrets candidates are redacted.
Pattern hits (4)
| Where | Rule | Match |
|---|---|---|
| src/webassets/assets_test.go:116 | download-piped-to-shell | []byte("curl https://getcroc.com | bash"), |
| web/src/blog-posts.ts:248 | download-piped-to-shell | "$ curl https://getcroc.com | bash", |
| web/src/blog-posts.ts:357 | download-piped-to-shell | "$ curl https://getcroc.com | bash", |
| web/src/blog-posts.ts:685 | download-piped-to-shell | "$ curl https://getcroc.com | bash", |
Installer scripts (1)
- scripts/install-benchmark-prereqs.sh, 185 lines, uses sudo, edits your shell profile; talks to api.github.com, go.dev, raw.githubusercontent.com, sh.rustup.rs
Worst known vulnerabilities (10 of 10)
| Advisory | Severity | Package | Summary |
|---|---|---|---|
| GHSA-2m5v-pch6-74hx | high | undici@7.30.0 | undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent |
| GHSA-4w7w-5xrc-9h26 | high | undici@7.30.0 | undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects |
| GHSA-qrxm-fqhp-jwvm | high | undici@7.30.0 | undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation |
| GHSA-xjj6-f33q-929c | high | undici@7.30.0 | undici vulnerable to Denial of Service via unhandled error on excessive content-encodings |
| GHSA-qxg6-89mg-rqv8 | moderate | @vitest/mocker@4.1.11 | Vitest: Code injection via unauthenticated manual mock registration |
| GHSA-xp26-3454-mjgp | moderate | @vitest/mocker@4.1.11 | Vitest: Windows backslash traversal bypasses the @vitest/mocker redirect allowlist fix |
| GHSA-4qv8-2p9j-2685 | moderate | undici@7.30.0 | undici vulnerable to Denial of Service via unbounded memory in the EventSource parser |
| GHSA-55wc-3pg8-jfw6 | moderate | undici@7.30.0 | undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor |
| GHSA-9fm3-97px-rjf6 | moderate | undici@7.30.0 | undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering |
| GHSA-f72v-6w45-q472 | moderate | undici@7.30.0 | undici vulnerable to Subresource Integrity bypass via non-lowercase algorithm tokens |
By the numbers
| Stars | 41K |
|---|---|
| Forks | 1,662 |
| Contributors | 175 |
| Commits | 2,603 |
| Open issues | 3 |
| Open pull requests | 5 |
| Releases | 232 |
| Latest release | v11.6.5 |
| Licence | MIT |
| Main language | Go |
| Project age | 9 years |
| Last push | Nov 20, 2026 |
| Tracked files | 517 |
| Lines of code | 104.3K |
| Checkout size | 7 MB |
Lines by language: Go 59.3K, TypeScript 20.5K, JSON 11.4K, CSS 4,231, Markdown 3,331, Python 2,152.
Questions
Is croc free?
Yes. It is free and open source under the MIT licence, and the public relay costs nothing to use. The README asks for support through GitHub Sponsors, and the getcroc.com website shows ads.
croc or a cloud drive link?
croc for a one-off transfer with no account, no size limit set by a cloud plan and nothing left on a server afterwards. A cloud drive is easier when the other person is not around to receive at the same time, though croc store now covers that with an encrypted link that expires.
Does croc work on Windows or a phone?
Yes. On Windows, install it with Scoop or Chocolatey and run it in PowerShell. On a phone, open getcroc.com in the browser, which can send to and receive from the command-line version.
Does croc send my data anywhere?
Your files go only to the other computer, encrypted, sometimes through the public relay, which cannot read them. croc also checks GitHub for updates once a day. Run your own relay with croc relay if you would rather not use the author's.
How do I uninstall croc?
Run brew uninstall croc or scoop uninstall croc. If you used the getcroc.com installer, delete croc and croc-update from /usr/local/bin with sudo rm.
This post is part of GitHub Tools, where every repository is cloned and scanned before it is written up. The scan is a snapshot of one commit on one day; the repository has moved on since, so check it before you install.
