Bitwarden Workertools

Bitwarden Workertools is a Docker image containing the Bitwarden command-line tools for running Bitwarden tasks as an Octopus Deploy execution container.

  • Development
  • Security
Bitwarden Workertools is a Docker image containing the Bitwarden command-line tools for running Bitwarden tasks as an Octopus Deploy execution container.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

40/100 Fair

Maintained
No data
Popular
No data
Easy to install
250 install platforms, install notes, Docker image
Light to run
602 GB minimum RAM, runs on ARM

Based on 2 of 4 factors.

No GitHub repository data collected yet.

Resources & Compatibility

Minimum requirements: 2 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the Bitwarden CLI first This server works by running the Bitwarden command-line tool, called bw. If bw is not installed on the computer running the server, Bitwarden calls fail with errors like spawn bw ENOENT, which means the tool could not be found. source
  • Add your BW_SESSION sign-in token In your MCP client settings (the app that talks to this server), set BW_SESSION to a real Bitwarden CLI session token. This is the token the server uses to sign in as you, and without it the server cannot access your Bitwarden account. source
  • Only use a local build if you built it If you are just installing it normally, avoid the node dist/index.js setting unless you have already run the local build steps. That file is only created by building from source, so pointing to it without a build leaves the client with nothing to start. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Will Bitwarden tooling work if the bw CLI is missing from the execution container?

No. The tooling runs the Bitwarden CLI, and if bw is not installed the calls can fail with errors like spawn bw ENOENT, meaning the tool could not be found.

What Bitwarden credential should be set so the tooling can access an account?

Set BW_SESSION to a real Bitwarden CLI session token. The server uses that token to sign in as you, and without it it cannot access your Bitwarden account.

Can the tooling be pointed at a local build if the project was not built first?

No. Avoid the node dist/index.js setting unless you have already run the local build steps, because that file is only created by building from source.

What domain should be used when generating certificates for a self-hosted Bitwarden domain?

Use the local domain you intend to use, such as bitwarden-host.lan, during certificate generation. The example accesses the instance over https on port 5880.

Answers sourced from github.com, github.com, github.com, www.reddit.com

Community

Collected 48 days ago - public community threads