Gooseplicant

Downloads

Download Gooseplicant

One kit for every install path and both editions, Gooseplicant and Gosling: the full source, the prebuilt web apps and the one-server setup script. Set it up on one server with ./goose setup, use it with Docker or Node.js by hand, or deploy it to Cloudflare Workers.

Version 0.7.0

Latest Released

Also: SHA256SUMS · manifest.json · always-current links live under /downloads/latest/.

What's new in 0.7.0

  • Fix an applicant's name. Recruiters and admins can edit a candidate's first and last name from the applicant panel in Gooseplicant and Gosling (the pencil next to the name). The new name applies to every application from that person and to search, shows on the Activity tab, and is recorded in the audit log (candidate.renamed). New API: PATCH /candidates/:id with { firstName, lastName } (both editions).
  • Names that look like a job title, a school or a company are flagged. Applicants sometimes type the position ("Forklift Operator") or their school ("Austin Community College") into the name fields. Those rows get a Check name badge in the inbox (a flag icon in Gosling), and the applicant panel explains what looks wrong with an Edit name button. The check is a hint only: nothing is blocked. Common surnames that are also trades (Baker, Cook, Mason, Porter, Driver...) are not flagged. Lists and details carry nameFlag ("jobTitle" | "school" | "company" | null).

Every release · How to update

Verify your download

Every release ships a SHA256SUMS file. Check the archive against it before you unpack.

  1. Download the archive and the checksum file into the same folder
    Terminal
    curl -LO https://gooseplicant.goosenotes.dev/downloads/0.7.0/gooseplicant-0.7.0.tar.gz
curl -LO https://gooseplicant.goosenotes.dev/downloads/0.7.0/SHA256SUMS
  2. Check it

    On macOS or Linux, check the archive you downloaded:

    Terminal
    grep ' gooseplicant-0.7.0.tar.gz$' SHA256SUMS | shasum -a 256 -c

    It prints gooseplicant-0.7.0.tar.gz: OK. If you downloaded both archives, shasum -a 256 -c SHA256SUMS checks them all; on Linux sha256sum -c works the same way.

    On Windows (PowerShell), compare the output with the SHA-256 shown above:

    PowerShell
    (Get-FileHash .\gooseplicant-0.7.0.zip -Algorithm SHA256).Hash.ToLower()
  3. Unpack it
    Terminal
    tar -xzf gooseplicant-0.7.0.tar.gz
cd gooseplicant-0.7.0

    Then follow INSTALL.md in the kit, or the guides here: One server (recommended), which continues with cd gooseplicant-0.7.0/deploy and ./goose setup; or by hand with Docker, Node.js or Cloudflare.

System requirements

Pick one runtime. Each needs a way to sign HR people in and, if you want to send email, a mail service.

Install pathYou need
One server (recommended)A Linux machine (or a Mac, for trying it) with Docker Engine and the Compose v2 plugin, openssl and curl; a domain whose DNS is on Cloudflare (free plan is fine) and an API token for it. Sign-in (Authelia) and HTTPS (Caddy) are included. Optional: Tailscale for staff working from home, SMTP for sign-in codes.
DockerDocker with BuildKit (the image is built from the kit) and Docker Compose for the proxy example. The image is based on Node.js 26. An authenticating reverse proxy in front.
Node.jsNode.js >=22.18 and npm, a process supervisor such as systemd, disk space for the SQLite database and uploads, and an authenticating reverse proxy in front.
CloudflareA Cloudflare account with a domain (zone) on it, Workers, D1, R2 and Cloudflare Zero Trust (Access). Node.js >=22.18 and npm on your machine to run Wrangler.
Email (optional)SMTP or a Microsoft 365 mailbox via Microsoft Graph (self-hosted), or Microsoft Graph (Cloudflare).

Cloudflare plans. Nothing in the code requires a paid Workers plan: it uses D1, R2, a Cloudflare Access application, a Cron Trigger and Workers Static Assets. Free tiers have usage and per-request CPU limits, and some products ask for a payment method before you enable them, so check Cloudflare's current pricing and limits for your expected volume.

What's in the kit

  • INSTALL.md and README.md: the short version of the guides on this site.
  • deploy/: the one-server setup. goose (the setup and maintenance script), compose.yml (Gooseplicant, Authelia, Caddy and cloudflared), caddy/Dockerfile (Caddy with the Cloudflare DNS plugin), templates/ for the generated configuration, README.md and its tests. Your settings, secrets and backups are created here by ./goose setup; they are never part of a release. See Set up on one server.
  • apps/node/: the self-hosted runtime, its Dockerfile, docker-compose.example.yml and .env.example.
  • apps/cloudflare/: the Worker, wrangler.toml (with placeholders) and .dev.vars.example.
  • packages/core, packages/http: the shared domain logic and HTTP layer, as TypeScript sources that Node.js runs directly.
  • packages/import: the email and PDF reader behind Import, which runs in the browser.
  • packages/ui/dist: the prebuilt web apps, the Gooseplicant HR app and Gosling (their sources are included too).
  • docs/ARCHITECTURE.md, docs/LITE.md (the Gosling design), LICENSE and THIRD_PARTY_NOTICES.md.

Older versions

License

Licensing terms TBD. The kit includes a LICENSE file with the terms that apply to that release.