SkySend

Share end-to-end encrypted Markdown notes, files, code and passwords/keys, or request secrets from others. Set a password, expiration time and/or maximum views. No account necessary. Self-hostable and has a client and admin CLI.

Open Source

SkySend Source Code

Author

Skyfay

Description

Minimalist, end-to-end encrypted, self-hostable file and note sharing. Zero-knowledge server - files and notes are encrypted in the browser before upload. No accounts, no telemetry, built for speed and security.

#aes-256-gcm#docker#encryption#end-to-end-encryption#file-sharing#privacy#react#s3-storage#self-hosted#typescript#zero-knowledge

Homepage

https://skysend.app

Repository

  • LicenseAGPL-3.0
  • Created06 Apr 26
  • Primary languageTypeScript
  • Size9,215 KB
  • Stars459
  • Forks27
  • Watchers459

Language Usage

Language Usage

Project Health

  • Last commit1 day ago
  • Open issues2
  • Latest releasev3.3.0

Recent Commits

  • Manu(10 Nov 26)

    Release v3.3.0: trusted proxies, Russian and Ukrainian, reloadable links and security hardening (#110) ## Problem SkySend v3.2.0 had several security holes found in the audit of 2026-11-07 and a report on presigned S3 URLs. A client reaching the server port directly could fake its IP and dodge lockouts. One bad upgrade request could crash the server. The CLI could run files received into the current folder. Note and file links also lost their key on reload, and code blocks lost indentation. ## Solution This release (v3.3.0) closes these holes, keeps the link key in the address bar, fixes code block rendering and adds Russian and Ukrainian. It merges `dev` into `main`. ## Changes - **Trusted proxies**: new `TRUSTED_PROXIES` option. With `TRUST_PROXY=true`, `X-Forwarded-For` and `X-Real-IP` count only on a connection from loopback or private networks by default. Invalid forwarded values fall back to the socket address. - **Server hardening**: - An upgrade guard answers 400 to anything but the two WebSocket upload routes and keeps bad sockets from crashing the process. - `rejectHead` returns 405 for HEAD on download routes. - `requireJson` returns 415 for non-JSON bodies on POST routes. - SQLite `secure_delete` is on. - The quota HMAC key stays in memory only, and quotas reset on restart. - The OIDC callback query is cut from logs. - Static path extension check is linear instead of a backtracking regex. - **S3**: presigned URLs default to 60 s (max 900 s) and never outlive the upload. An abort while waiting for memory no longer double-returns memory. - **CLI**: - Compiled binaries no longer autoload `bunfig.toml` or `.env`. - Windows tools (`clip`, `rundll32`, `cmd`, `timeout`) run by full path through `systemTool()`. - **Docker**: the entrypoint uses `chown -h` so it does not follow a symlinked uploads dir. - **Report Worker**: bounded body, reasons, comment and URL. Unsafe mailto characters in the reply address are refused. Only an exact localhost origin counts as dev. - **Web**: - Note and file pages keep the key in the URL fragment (`useLinkSecret`), and a hash change reloads. - Code blocks keep indentation and multi-line token color (`highlightedLines`). - Added Russian and Ukrainian translations. - **Docs and release**: docs for `TRUSTED_PROXIES`, S3 expiry, API status codes and the threat model. Versions bumped to 3.3.0 and the changelog collected. - **Tests**: new tests for the upgrade guard, trusted proxies, `requireJson`, HEAD rejection, `secure_delete`, quota key, presigned expiry, `highlightedLines`, `windows-tool` and the build scripts, plus an e2e reload spec. ## Breaking notes - Setups where the proxy connects from a public address must set `TRUSTED_PROXIES`. - `S3_PRESIGNED_EXPIRY` above 900 now fails at startup.

  • Manu(10 Nov 26)

    Release v3.3.0: bump versions and collect changelog fragments - Sync every package.json and apps/client/src/version.ts to 3.3.0. - Write the v3.3.0 block into docs/changelog.md from the unreleased fragments, including the TRUSTED_PROXIES and S3_PRESIGNED_EXPIRY update warnings. - Delete the collected fragments under changelog/unreleased/.

  • Manu(10 Nov 26)

    Merge origin/main into dev Brings the v3.2.0 release merge and the two instances worker commits of main into dev. Their content is already on dev, so no file changes.

  • Manu(10 Nov 26)

    Shorten presigned S3 URLs and cap them at the upload expiry - A presigned URL works any number of times until it expires, so on S3 the download count counts the URLs handed out, not the fetches (GHSA-ghcm-gq78-wggw). Narrow that window instead of proxying downloads. - S3_PRESIGNED_EXPIRY defaults to 60 seconds instead of 300 and accepts at most 900. A higher value stops the server at startup. - getPresignedDownloadUrl takes the expiry of the upload and never signs a URL that outlives it. Applies to /api/download and the inbox download. - Correct the S3 storage comment that claimed the TTL enforces the limit, and document the remaining window in the architecture page and the env var references. - Tests cover the config bounds, the TTL clamp read from X-Amz-Expires and the expiry both routes hand to the storage.

  • Manu(10 Nov 26)

    Keep the secret in the URL fragment on note and file pages (#109) ## Summary Note and file pages now leave the key in the address bar. Before, the page wiped the key from the URL as soon as it loaded a note or started a download. A reload, a restored tab or a copied address then opened a page that could not decrypt anything. Now those all open the link again. ## Changes - Add a `useLinkSecret` hook that reads the key from the URL fragment once at mount and returns it. It also reloads the page when the fragment changes by hand, so a key added to the address bar of an open page opens the link right away instead of keeping the old state. - `NoteView` and `Download` use the hook. The `history.replaceState` calls that cleared the fragment are removed, along with the comments that explained them. - Add a changelog fragment under `changelog/unreleased/` (Changed and Tests). - Add Playwright e2e tests in `e2e/tests/reload.spec.ts`: - A note link keeps its key through a reload. - A file link keeps its key after a download, and a reload downloads the file again with the same content and tier. - A key added to the address bar of an open page opens the link. The secret still stays in the fragment, which browsers never send to the server, so the zero-knowledge boundary is unchanged. The trade-off is that the key now remains visible in the address bar and browser history. ## Testing The new e2e tests cover reload and late key addition for notes and files. I did not run them while writing this description, so the results are TODO.

  • Manu(10 Nov 26)

    Preserve code indentation and multi-line token color in note code blocks (#108) ## Problem Code blocks in a note lost their leading spaces and tabs, because the table cell they are shown in collapses whitespace. Indented code lost its shape. Also, a comment or string that runs over several lines only had its color on the first line. ## Fix The code cell now keeps whitespace as written. The highlighted markup is split into lines in a way that closes a multi-line token at the end of each line and reopens it on the next, so every line keeps its color. ## Changes - `NoteBlocks.tsx`: the code cell uses `whitespace-pre`, and the lines come from the new `highlightedLines` helper. - `highlight.ts`: add `highlightedLines`, which splits the sanitized markup into balanced per-line markup. Only the spans the sanitizer left are moved, and the text between them stays escaped. - Unit tests for `highlightedLines`: indentation, multi-line tokens, nested spans stay balanced, escaped markup stays escaped. - E2E test: the note test now checks that the indentation of a code line survives for the recipient. - Changelog fragment `changelog/unreleased/Skyfay-code-note-indent.md` with two bug fix entries. ## Testing - Added unit tests in `apps/web/tests/lib/highlight.test.ts`. - Extended the Playwright test in `e2e/tests/notes.spec.ts`.

  • Manu(10 Nov 26)

    Keep the secret in the URL fragment on note and file pages (#102) - Add useLinkSecret hook that reads the key from the fragment at mount and leaves it in the address bar, so a reload, a restored tab or a copied address opens the link again. - Reload the page when the fragment changes by hand, so a key added to the address bar later starts the share over with the new key. - Drop the history.replaceState calls in Download and NoteView that cleared the fragment. - Add e2e tests for reloading a note and a file link and for adding the key to an open page, plus the changelog fragment.

  • Manu(10 Nov 26)

    Read line text through the DOM in the highlightedLines test CodeQL flagged the regex that stripped tags as incomplete multi-character sanitization. The test now reads the text a line shows through a table cell, the way the code view renders it.

  • Manu(10 Nov 26)

    Preserve code indentation and multi-line token color in note code blocks (#103) - Table cells collapse leading whitespace, so indented code lost its shape. The code cell now uses whitespace-pre. - Add highlightedLines, which closes open highlight spans at each line end and reopens them on the next line, so multi-line comments and strings keep their color on every line. - Extend the unit tests and the notes e2e test to cover indentation, spanning tokens and escaping. - Add a changelog fragment for the fix (#103).

  • Manu(10 Nov 26)

    Close the server holes found in the audit of 2026-11-07 (#107) ## Problem A full audit of the server (2026-11-07) found two high, three medium and several low issues. Every one was reproduced against the server started from source on loopback: - **Crash (high, 2x):** `injectWebSocket` attached the upgrade listener of `@hono/node-ws` to the whole HTTP server. One unauthenticated request with an `Upgrade` header and the target `//` (or `http://[`) threw in `new URL` and the unhandled rejection ended the process. An upgrade on any path followed by a TCP reset crashed it too, because Node hands the socket over without an error handler and the listener adds none. - **Lockout reset (medium):** each crash and the `restart: always` restart cleared the in-memory password lockout and rate limiter on demand. - **Leak through upgrades (medium):** the listener ran the GET route of any path and dropped its response. An upgrade to `/api/download/:id` counted a download and kept a file descriptor open, also pinning the disk space of a deleted upload until a restart. - **HEAD (medium):** Hono answers HEAD with the GET handler and drops the body. On the download routes that counted a download and leaked a descriptor per request. - **Cross-site POSTs (low):** `c.req.json()` parses any Content-Type, so another site could send a `text/plain` simple request without a preflight. A wrong token counted against the visitor's lockout of a share, and request creation used up their daily limit. - **Other lows:** the SPA fallback regex backtracked quadratically on paths of many dots, deleted rows stayed readable in the SQLite file, an S3 upload aborted while waiting for `PartMemory` released its `FillMemory` twice, and the entrypoint's `chown` followed a symlink at `UPLOADS_DIR`. The default nginx config of the reverse proxy guide forwards `Upgrade` on `location /`, so a proxy did not protect against the crash. ## Solution - `guardUpgrades` (`lib/upgrade-guard.ts`) registers the node-ws listener on a private emitter and puts a guard in front: every upgrade socket gets an error handler, anything but a WebSocket upgrade of `/api/upload/ws` or `/api/request/:id/upload/ws` gets `400` before any route runs, and a failing listener only destroys its own socket. - `rejectHead` answers `405` with `Allow: GET` on `/api/download/:id` and `/api/inbox/:id/file/:uid`. - `requireJson` answers `415` on the seven POST routes that read a JSON body, before any lockout or limit bookkeeping. Every released web app and CLI back to v2.12 sends `application/json`. - A linear `hasFileExtension` replaces the regex, `secure_delete = ON` for the database, an abort check in `S3Storage.takePart` and `bufferSize` reset in `discardPart`, `chown -h` in the entrypoint. ## Changes - **server**: `lib/upgrade-guard.ts`, `middleware/reject-head.ts`, `middleware/require-json.ts`, `hasFileExtension` in `lib/static-assets.ts`, `secure_delete` in `db/index.ts`, abort check in `storage/s3.ts`, wiring in `index.ts` and the routes. - **docker**: `chown -h` on `UPLOADS_DIR`, with a log line when it is a symlink. - **docs**: `405` and `415` in the API reference, the upgrade rule on the download page. - `apps/server/CLAUDE.md`: rules so new routes keep the three guards. - Changelog fragment `changelog/unreleased/Skyfay-server-audit-fixes.md`. ## Testing - `pnpm validate` passes (lint, typecheck, tests). - New tests for each fix, each checked to fail without it: the guard against a real `http.Server` with `@hono/node-ws` (400 on other routes and bad targets, survives resets, still upgrades the WS route, contains a throwing listener), HEAD on both download routes, `text/plain` on note view and password and on request creation, the regex equivalence and speed, no deleted row left in the database file, and the S3 abort while waiting. - Replayed the audit's attacks against the real server from this branch: `//` and `http://[` upgrades answer 400, 20 upgrades with reset leave it up, an upgrade to a download route answers 400, HEAD answers 405, a cross-site `text/plain` view answers 415, `/api/upload/ws` still answers 101, a 16 000-dot path takes 1.8 ms. - The entrypoint change was only syntax-checked, no container restart was run. Left open on purpose: reclaiming orphaned blobs at startup (could delete the blobs of another instance on a shared `UPLOADS_DIR`) and stopping chunk bodies still in flight when a session ends (low, only while the connections stay open). Independent of #106, both merge into `dev` without conflicts. ## Follow-up from the Worker audit of the same day The later run of the audit (run-4, report Worker and the request log) added four small changes to this branch: - The request log cuts the query string of every `/auth/` path, so the OIDC authorization code no longer lands in the log (`request-logger.ts`, with a test). - The report Worker refuses a reply address with `? # & % /`, which the website never sends but a direct call could, and which would turn the `mailto:` link of the report into a prefilled reply. - The report Worker bounds the body (16 KiB) before parsing it, and reasons (7 of at most 100 chars), comment (5000) and URL (2048). - Only `http://localhost` with an optional port counts as the development origin, instead of any origin starting with that prefix.

  • Manu(10 Nov 26)

    Cut the OIDC callback query from the log and harden the report Worker The request logger kept the query string of /auth/callback, so the authorization code of every login reached the log. Every /auth/ path is now cut after its first segment, with a test. The report Worker refuses a reply address with mailto delimiters, which could preload recipients, subject or body of the operator's reply, bounds the body before parsing it plus the reasons, comment and URL, and only an exact localhost origin counts as a development origin.

  • Manu(10 Nov 26)

    Close binary planting, bunfig autoload, TRUST_PROXY and quota key holes (#106) ## Problem A security audit found four holes, two in the CLI binary and two in the server: - **CLI on Windows:** `clip`, `rundll32`, `cmd` and `timeout` were started by bare name. Windows searches the current folder first, and downloads land there under the name the sender chose, so a received `clip.exe` (or `tput.exe`, run by a dependency of Ink) ran instead on copy, browser opening, login, update or the start of the interactive mode. - **CLI binary:** `bun build --compile` reads `bunfig.toml` and `.env` from the current folder by default. A `bunfig.toml` with `preload = ["./x.js"]` and the script next to it, two received files, ran code on the next `skysend` in that folder. This also affects the released v3.2.0 binaries. - **Server, `TRUST_PROXY`:** with `TRUST_PROXY=true` and port 3000 published as the docs showed, `X-Forwarded-For` was trusted from any peer. A client could send a new address with every password guess and was never locked out. - **Server, quota key:** the HMAC key for upload quotas was stored in `quota_state` next to the hashes, so a copy of the database gave back every IPv4 address, which contradicts the threat model. ## Solution - The CLI starts the Windows tools by their full System32 path and sets `NoDefaultCurrentDirectoryInExePath=1` at startup, which Bun honours at runtime and which also covers `tput`. - Every compile script passes `--no-compile-autoload-bunfig --no-compile-autoload-dotenv`. A test keeps the flags on all of them. - Forwarded headers count only on a connection from `TRUSTED_PROXIES`. Unset, these are loopback and the private networks (RFC 1918, 100.64/10, link-local, fc00::/7), so existing setups behind a local or Docker proxy keep working. A value that is no IP address falls back to the socket address. - The quota key lives only in memory, and `quota_state` and `quota_usage` are cleared on start. Quotas now start afresh on a restart. ## Changes - **client**: `lib/windows-tool.ts` with `systemTool()`, used by clipboard, OIDC browser opening and update. `NoDefaultCurrentDirectoryInExePath` in `index.ts`. Autoload flags in the six `build:*` scripts, `tests/build-scripts.test.ts`. - **server**: `lib/trusted-proxies.ts`, peer check in `middleware/rate-limit.ts`, new `TRUSTED_PROXIES` in `config.ts`. In-memory key in `middleware/quota.ts`. - **docs**: `TRUSTED_PROXIES` in the env var reference, `.env.example` and `.env.dev.example`. The reverse proxy guide explains it, binds the published port to `127.0.0.1` and covers the Docker IPv6 proxy case. Rate limiting and threat model pages updated. - Changelog fragment `changelog/unreleased/Skyfay-windows-spawn-paths.md` with a "Before updating" note for proxies that connect from a public address. ## Testing - `pnpm validate` passes (lint, typecheck, tests). - Binary planting reproduced and the fix verified end to end on a Windows test host with the real Bun binary. A planted `bunfig.toml` is ignored by the rebuilt binary on Linux and Windows. - New tests for the trusted proxy list, the socket fallback, the warning on ignored headers and the in-memory quota key. - Known leftover, not part of this PR: the update `.bat` runs `timeout.exe` detached without a console, so its 2 s wait does not happen. Independent of #107, both merge into `dev` without conflicts.

  • Manu(10 Nov 26)

    feat(i18n): add Russian and Ukrainian translations (#104) Adds Russian (ru) and Ukrainian (uk) translations. - New locale files: apps/web/src/i18n/ru.json, apps/web/src/i18n/uk.json - Registered both languages in apps/web/src/i18n/index.ts - Added both to the language switcher (LanguageSwitcher.tsx)

  • Manu(10 Nov 26)

    Add the changelog entry and list Russian and Ukrainian in the docs

  • Manu(08 Nov 26)

    Close the server holes found in the audit of 2026-11-07 - Attach the @hono/node-ws upgrade listener only through a guard. It gives every upgrade socket an error handler, answers 400 to anything but a WebSocket upgrade of the two upload routes and contains a failing listener to its own socket. One upgrade with target "//" or a TCP reset crashed the process before, which also reset the password lockout, and an upgrade to a download route leaked a file stream. - Answer HEAD with 405 on the download and inbox file routes. Hono ran the GET handler for it, which counted a download and left the file descriptor open until a restart. - Require application/json on every POST that reads a JSON body. A cross-site text/plain POST skipped the CORS preflight and counted as a lockout failure or used up the daily file request limit. - Replace the SPA fallback regex with a linear check. It backtracked quadratically on paths of many dots. - Turn on SQLite secure_delete so deleted rows do not stay readable in the database file. - Stop an S3 upload aborted while it waits for PartMemory from taking its part, which released its FillMemory a second time. - Use chown -h on UPLOADS_DIR in the entrypoint so a symlink planted by the runtime user is never followed by root.

  • Manu(07 Nov 26)

    Close three security holes in the CLI binary and the server - CLI on Windows: start clip, rundll32, cmd and timeout by their full System32 path and set NoDefaultCurrentDirectoryInExePath at startup. Windows searched the current folder first, where downloads land under the sender's name, so a received clip.exe or tput.exe ran instead. - CLI binary: compile with --no-compile-autoload-bunfig and --no-compile-autoload-dotenv. A bunfig.toml in the current folder could preload a script, so two received files ran code on the next start. A test keeps the flags on every compile script. - Server: forwarded client addresses count only on a connection from TRUSTED_PROXIES, by default loopback and the private networks. With TRUST_PROXY=true and port 3000 published as the docs showed, anyone could send a new X-Forwarded-For with every password guess and was never locked out. A value that is no address falls back to the socket. - Server: the HMAC key of the upload quota stays in memory. Stored next to the hashes, a copy of the database gave back every IPv4 address. Quotas now start afresh on a restart. - Docs, env templates and the changelog fragment cover TRUSTED_PROXIES, the 127.0.0.1 binding behind a local proxy and the quota key.

  • Ruslan Semenov(06 Nov 26)

    fix(i18n): add plural forms and align upload wording

  • Ruslan Semenov(06 Nov 26)

    feat(i18n): add Russian and Ukrainian translations

  • Manu(25 Oct 26)

    Send a User-Agent from the instances worker A Worker's fetch sends no User-Agent, and Cloudflare's Browser Integrity Check answers such requests with 403. skysend.cyberjake.xyz sits behind such a zone, so the worker listed it as offline although it was up. The worker now identifies itself as SkySend-Instances with a link to the instance list, which also lets operators recognise and allow the check.

  • Manu(25 Oct 26)

    Send a User-Agent from the instances worker A Worker's fetch sends no User-Agent, and Cloudflare's Browser Integrity Check answers such requests with 403. skysend.cyberjake.xyz sits behind such a zone, so the worker listed it as offline although it was up. The worker now identifies itself as SkySend-Instances with a link to the instance list, which also lets operators recognise and allow the check.

  • Manu(24 Oct 26)

    Add skysend.cyberjake.xyz to the public instances list - Register the new US instance in instances.json with its contact and abuse address so operators and users can find it. - Add the changelog fragment for the docs entry.

  • Manu(24 Oct 26)

    Add skysend.cyberjake.xyz to the public instances list - Register the new US instance in instances.json with its contact and abuse address so operators and users can find it. - Add the changelog fragment for the docs entry.

  • Manu(23 Oct 26)

    Release v3.2.0: rebuilt CLI, shared transfer package and security fixes (#101) ## Summary This is the v3.2.0 release, merging `dev` into `main`. The end-user CLI is rebuilt as a full-screen tabbed app with file request support. Upload, download, note and request logic now lives in one shared package, `@skysend/transfer`, which the web app and the CLI both use. The release also carries a round of security hardening. ## Changes ### CLI - Interactive mode is now a full-screen tabbed TUI (send, receive, note, links, settings) in the web app's colors, with a file picker, folder upload, progress with speed, and QR codes. - New `skysend inbox` command, plus sending into file requests from the CLI. - `skysend delete` also removes the entry from local history. - Login and browser opening are hardened (random callback path, no `cmd.exe` on Windows, missing browsers handled). - File names in inbox JSON output are cleaned. ### Shared transfer package - New `packages/transfer` with the API client, links, zip, upload pipeline (WebSocket and HTTP chunks), download decryption, notes and file request logic. - The web app, the CLI and the server's contract tests use it. The zip code moved here from the web app. - New API contract tests run the real server routes against the shared client. ### Security and hardening - The base nonce of the encrypted stream is also stored in the authenticated metadata, and downloads check the stream header against it (web, service worker, CLI). - Password lockout closes a race where parallel or held-back requests could evaluate more guesses than allowed. - WebSocket upload limits: max payload and a stall timeout for slow frames. - S3 uploads no longer use `lib-storage`. Part memory is bounded and overflow goes to `DATA_DIR/tmp/s3-parts/`. - `/auth` routes are marked `Cache-Control: no-store`. - An HTTP `OIDC_ISSUER` is now refused unless `OIDC_ALLOW_INSECURE_ISSUER=true` is set (new option, contributed in #96). - The installer scripts and `skysend update` now require a matching checksum and never install an unverified binary. - Markdown in notes is limited in length and budget to avoid quadratic parse time. - Trailing slash trimming uses a linear-time helper instead of a regex. - The instances worker caps how many bytes it reads from an instance response. - The DevTools check in downloads only counts the height gap, not the width gap. ### Docs, tests and CI - New developer guide page "Transfer Core", plus updates to the CLI, S3, reverse proxy, OIDC, rate limiting, installation and troubleshooting docs. - Changelog entry for v3.2.0. All package versions bumped to 3.2.0. - Compat snapshot of v3.1.0 for link compatibility e2e tests. - New CLI e2e tests (including file requests and OIDC login). Coverage, build and Docker steps include the transfer package. - Playwright browser install in CI is cached and retried, the Docker wait in E2E is longer, and the release build always pulls the base image. ## Testing No test results are included in the provided material. CI (`pnpm validate`) should confirm.

  • Manu(23 Oct 26)

    Release v3.2.0 with the rebuilt CLI and security fixes - Bump every package and the client version constant to 3.2.0. - Collect the seven unreleased changelog fragments into the v3.2.0 block of docs/changelog.md and delete them.

  • Manu(23 Oct 26)

    Stop counting width gap as open DevTools in the download check - A sidebar in Firefox (vertical tabs, bookmarks), Chrome or Edge narrows the page like side-docked DevTools. The width gap made isDevToolsOpen() fire for these users and blocked downloads with a warning. - Only the outer/inner height gap counts now. Side-docked and undocked DevTools stay undetected, which the doc comment says. - Tests cover the bottom-docked case and a wide vertical-tabs sidebar. - Set agentRules to false in the website's next.config.ts so `next dev` does not write an AGENTS.md. The agent guide is CLAUDE.md. - Add a changelog fragment for the bug fix (#99).

  • Manu(23 Oct 26)

    Always pull the base image in the release build Every release now ships the latest Node patch release of node:24-alpine, which currently is 24.22.1 with the fix for CVE-2026-111497.

  • Manu(23 Oct 26)

    Rework the CLI on a shared transfer package with a full-screen tabbed TUI and file request support (#100) ## Summary The web app and the CLI each had their own copy of the upload, download, note, link and API code, and the copies drifted apart. This PR moves that code into one shared package, `@skysend/transfer`, and rebuilds the CLI on top of it. The interactive mode becomes a full-screen app with tabs, and the CLI can now send into and read file requests. ## Changes ### Shared package `@skysend/transfer` - New package with the API client (Zod-parsed answers, `ApiError`), share links, zip (moved from the web app), the upload pipeline (WebSocket or HTTP chunks), checked download decryption, notes, and both sides of file requests. - The web app now uses it for uploads, downloads, notes, links and request handling. The upload worker only adapts it to `File` and messages. - The CLI uses it too. Its own `fflate` zip, `ws-upload`, `url` and `temp-file` code is removed. - `apps/server/tests/api-contract.test.ts` reads the answers of the real routes with the shared client, so a server change the clients could not read fails there. - Wired into the build (`Dockerfile`, workflows, `tsconfig.json`, `pnpm-lock.yaml`), version sync, and Codecov (new `transfer` flag). ### CLI - Interactive mode is a full-screen app with tabs for Send, Receive, Note, Links and Settings. It uses the Graphite theme of the web app and the accent color of the server. - First start offers the public instances from instances.skysend.app and a field for your own server. - Folders upload as a zip that keeps their structure. - After an upload the TUI shows the link as a QR code and a clickable link, and copies it to the clipboard (system tool plus OSC 52, so it works over SSH). - Upload progress shows time left and a speed curve, and can be cancelled. - Notes can hold several blocks. - New `skysend inbox` command and `skysend upload --to <link>` send into and read file requests. - WebSocket uploads are on again unless switched off per server (`--no-ws`). A failed handshake falls back to HTTP. - `skysend delete` also removes the entry from the local history, but only after the server deleted it. - OIDC login hardening: the callback uses an unguessable path, and opening the browser no longer goes through `cmd.exe` on Windows. The login also survives a missing browser. - Names in inbox JSON, including zip entry names, are cleaned. `--json` errors are written as plain JSON lines. ### Docs and tests - New developer guide page "Transfer Core". Updated CLI user docs, file request docs, testing docs, architecture and the `CLAUDE.md` guides. - Reverse proxy guide: Nginx now uses `proxy_buffering on` with `proxy_max_temp_file_size 0`. A troubleshooting entry explains slow downloads with buffering off. - New unit tests in `packages/transfer` and for the CLI commands and TUI helpers. New e2e tests `cli-requests.spec.ts`, plus CLI cases in `cli.spec.ts` and an OIDC login case in `config.spec.ts`. The benchmark can run with `--client cli`. - Changelog fragment: `changelog/unreleased/Skyfay-cli-rework.md`. ## Testing - TODO: results of `pnpm validate` and `pnpm test:e2e` are not recorded here.

  • Manu(23 Oct 26)

    Add API client tests and wait longer for Docker in E2E - Add tests for the shared transfer API client: URLs, per-route tokens, error mapping, older-server defaults, S3 downloads and chunked uploads. - Cover briefFits, the sshkey block and an unparseable request template. - Test the missing Argon2id error in useDownload and the kept file URL in pastedPaths. - Raise the E2E `docker info` timeout from 10 s to 90 s, since a CI runner still clearing its disk answered too late and skipped the Docker-based tests.

  • Manu(23 Oct 26)

    Move Playwright browser install in E2E CI into a retried script - Replace the inline install loops in both E2E jobs of validate.yml with e2e/scripts/install-browser.sh, so the logic lives in one place. - Run install-deps as root under `timeout --kill-after`, so the timeout reaches apt-get itself. Through Playwright's own sudo it left apt-get running, which held the dpkg lock and failed every retry. - Keep the eight minute cutoff and three attempts for the stalling Ubuntu mirror, and document the script in the testing guide and e2e/CLAUDE.md.

  • Manu(23 Oct 26)

    Make Playwright browser install in E2E CI cached and retried - Cache ~/.cache/ms-playwright per browser and Playwright version, so the browser download is skipped while the version stays the same. - Cut each `playwright install --with-deps` attempt off after eight minutes and retry up to three times. The Ubuntu mirror of the runner sometimes delivers at 50 KB/s, which held a job in this step for half an hour. - Apply the same handling to the large-file job. - Add a changelog entry and a note in the testing reference.

SkySend Security

Security Advisories (6)

  • mediumPatched

    GHSA-rmc2-p8pp-4vmhUnauthenticated WebSocket upload-session flood: /api/upload/ws upgrade is exempt from the global rate limiter and uncapped (incomplete-fix sibling of GHSA-9rmm-v3p2-c26g)

  • mediumPatchedCVSS 6.1

    GHSA-5vjq-2637-p33fSkySend CLI creates its history file with world-readable permissions

  • mediumPatched

    GHSA-rxxj-c5wr-phqpOffline password guessing on password-protected files

  • highPatchedCVSS 8.8

    GHSA-2gh8-5c87-87jxSkySend CLI path traversal on download

  • highPatchedCVSS 7.5

    GHSA-9rmm-v3p2-c26gChunk upload endpoint buffers the whole request body in memory before checking its size, and is exempt from rate limiting (unauthenticated memory exhaustion)

  • lowPatchedCVSS 2.4

    GHSA-w3p6-2vcf-mmv9Truncated downloads are accepted as complete files (expectedPlaintextSize is never passed to createDecryptStream)

SkySend Website

Website

SkySend - End-to-End Encrypted File & Note Sharing

End-to-end encrypted, self-hostable file and note sharing service built for speed and security.

Redirects

Does not redirect

Security Checks

2 security checks failed (63 passed)

  • Domain Recently Created
  • Domain Very Recently Created

Server Details

  • IP Address104.21.18.28
  • LocationSan Francisco,California,United States of America,NA
  • ISPCloudFlare Inc.
  • ASNAS13335

Associated Countries

  • USUS
  • CHCH

Safety Score

Website marked as safe

100%

Trackers

No known trackers found

Blacklist Check

skysend.app was found on 0 blacklists

  • AntiSocial Blacklist
  • Artists Against 419
  • Badbitcoin
  • Bambenek Consulting
  • CERT Polska
  • CoinBlockerLists
  • CRDF
  • CryptoScamDB
  • EtherAddressLookup
  • EtherScamDB
  • Fake Website Buster
  • MetaMask EthPhishing
  • NABP Not Recommended Sites
  • OpenPhish
  • PetScams
  • PhishFeed
  • PhishFort
  • Phishing.Database
  • PhishStats
  • PhishTank
  • Phishunt
  • RPiList Not Serious
  • Scam.Directory
  • SecureReload Phishing List
  • Spam404
  • StopGunScams
  • Suspicious Hosting IP
  • ThreatFox
  • ThreatLog
  • TweetFeed
  • URLhaus
  • ViriBack C2 Tracker

Website Preview

Website preview

SkySend Reviews

More Secret Sharing

About the Data: SkySend

Change History

Edit SkySend Data

You can edit SkySend's entry in this section of awesome-privacy.yml by submitting a PR to our GitHub repo.
Note that some of the information shown above has been aggregated from external sources, a list of these can be found data documentation.

Origin Data

Modify Data

API

You can access SkySend's data programmatically via our API. Simply make a GET request to:

https://api.awesome-privacy.xyz/v1/services/skysend

The REST API is free, no-auth and CORS-enabled. To learn more, view the API Docs or read the API Usage Guide.

Share SkySend

Help your friends compare Secret Sharing, and pick privacy-respecting software and services.
Share SkySend and Awesome Privacy with your network!