This repository houses the internal Bitwarden SDKs. We also provide a public Secrets Manager SDK.
The password manager SDK is not intended for public use and is not supported by Bitwarden at this stage. It is solely intended to centralize the business logic and to provide a single source of truth for the internal applications. As the SDK evolves into a more stable and feature complete state we will re-evaluate the possibility of publishing stable bindings for the public. The password manager interface is unstable and will change without warning.
Interested in contributing in a big way? Consider joining our team! We're hiring for many positions. Please take a look at our Careers page to see what opportunities are currently open as well as what it's like to work at Bitwarden.
cargo build
To build, you will need the following in your PATH:
- Python
- Clang
- We recommend installing this via the Visual Studio Build Tools
Please refer to our Contributing Docs for getting started instructions and architectural documentation.
You can also browse the latest published documentation:
- docs.rs for the public SDK.
- Or for developers of the SDK, view the internal API documentation which includes private items.
The project is structured as a monorepo using cargo workspaces. Some of the more noteworthy crates are:
bitwarden-api-api
: Auto-generated API bindings for the API server.bitwarden-api-identity
: Auto-generated API bindings for the Identity server.bitwarden-core
: The core functionality consumed by the other crates.bitwarden-crypto
: Crypto library.bitwarden-wasm-internal
: WASM bindings for the internal SDK.bitwarden-uniffi
: Mobile bindings for swift and kotlin using UniFFI.
We autogenerate the server bindings using openapi-generator. To do this we first need to build the internal swagger documentation.
The first step is to generate the swagger documents from the server repository.
# src/Api
dotnet swagger tofile --output ../../api.json ./bin/Debug/net8.0/Api.dll internal
# src/Identity
ASPNETCORE_ENVIRONMENT=development dotnet swagger tofile --output ../../identity.json ./bin/Debug/net8.0/Identity.dll v1
To generate a new version of the bindings run the following script from the root of the SDK project.
./support/build-api.sh
This project uses customized templates which lives in the support/openapi-templates
directory.
These templates resolves some outstanding issues we've experienced with the rust generator. But we
strive towards modifying the templates as little as possible to ease future upgrades.
Note: If you don't have the nightly toolchain installed, the build-api.sh
script will install it
for you.
This project recommends the use of certain developer tools, and also includes configurations for them to make developers lives easier. The use of these tools is optional and they might require a separate installation step.
The list of developer tools is:
Visual Studio Code
: We provide a recommended extension list which should show under theExtensions
tab when opening this project with the editor. We also offer a few launch settings and tasks to build and run the SDKbacon
: This is a CLI background code checker. We provide a configuration file with some of the most common tasks to run (check
,clippy
,test
,doc
- runbacon -l
to see them all). This tool needs to be installed separately by runningcargo install bacon --locked
.nexttest
: This is a new and faster test runner, capable of running tests in parallel and with a much nicer output compared tocargo test
. This tool needs to be installed separately by runningcargo install cargo-nextest --locked
. It can be manually run usingcargo nextest run --all-features
We use certain unstable features for formatting which require the nightly version of cargo-fmt.
To install:
rustup component add rustfmt --toolchain nightly
To run:
cargo +nightly fmt
Code contributions are welcome! Please commit any pull requests against the main
branch. Learn
more about how to contribute by reading the
Contributing Guidelines. Check out the
Contributing Documentation for how to get started with your
first contribution.
Security audits and feedback are welcome. Please open an issue or email us privately if the report
is sensitive in nature. You can read our security policy in the SECURITY.md
file.
We also run a program on HackerOne.
No grant of any rights in the trademarks, service marks, or logos of Bitwarden is made (except as may be necessary to comply with the notice requirements as applicable), and use of any Bitwarden trademarks must comply with Bitwarden Trademark Guidelines.