Download the PHP package christianrudde/vaultwarphpen without Composer
On this page you can find all versions of the php package christianrudde/vaultwarphpen. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download christianrudde/vaultwarphpen
More information about christianrudde/vaultwarphpen
Files in christianrudde/vaultwarphpen
Package vaultwarphpen
Short Description A password server for plain PHP hosting that works with the official Bitwarden apps: a PHP port of Vaultwarden.
License AGPL-3.0-only
Homepage https://github.com/Lumundi/kennword
Informations about the package vaultwarphpen
A password server for plain PHP hosting.
Works with the official Bitwarden apps.
www.kennword.org · Installation · Security review
A PHP port of Vaultwarden, the Bitwarden-compatible server
written in Rust. Kennword is a modified version of Vaultwarden: its Rust source, translated into PHP
on Laravel since October 2026, following Vaultwarden commit
6ed6921
(release 1.37.5). NOTICE.md names everything it is based on.
It is meant to run on an ordinary PHP host, without Docker, and to be a drop-in replacement for Vaultwarden: the same HTTP API for the official Bitwarden clients, the same database and the same environment variables, so an installation can move from Vaultwarden to Kennword and back.
Until version 0.2.0 it was called Vaultwarphpen; we renamed it so that it does not borrow Vaultwarden's name. Kennwort is German for password: Kennword keeps the German "kenn" (to know) and makes the rest English. Say it "KEN-word".
[!IMPORTANT] Kennword has not been independently audited. Its answers are compared with Vaultwarden's on every change, and it keeps Vaultwarden's database and data folder, so an installation can always go back. Security status says what is checked, what is open and how to run it with care.
Why a PHP port
At Lumundi, we run our company software exclusively in PHP, on managed servers. We liked Vaultwarden's approach so much, a lean self-hosted server for the official Bitwarden clients, that we decided to port it to PHP with the help of AI (see Credits).
Status
PARITY.md lists every route, setting, scheduled job, table, template and static asset of the pinned Vaultwarden version and whether it is ported. In short:
- Ported: the database schema for SQLite, MySQL/MariaDB and PostgreSQL, interchangeable with Vaultwarden's; registration and login with the master password; two-step login (authenticator, email, WebAuthn, YubiKey, Duo, recovery code); account management, devices and login with a device; folders and Sends; ciphers and attachments; the organization API (members, collections, groups, policies, account recovery, import and export, API keys, the event log); emergency access; mails over SMTP or sendmail; Vaultwarden's scheduled jobs; the admin panel; the web vault (from Vaultwarden's setup); live notifications over WebSocket, served by an optional daemon (installation), and mobile push through Bitwarden's relay; website icons, fetched and cached like Vaultwarden's or redirected to an external icon service.
- Not ported: attachments and Send files in anything but a local folder (Vaultwarden's S3 and other OpenDAL backends), TPM and Android key attestation for WebAuthn (the clients send it only when asked, which Vaultwarden does not do) and the SMTP debug log. A few settings have no effect in PHP, such as the database pool sizes; Configuration lists every difference.
Security status
What is checked
- Behaviour: every ported route is compared with Vaultwarden itself. The differential tests send the same requests to both servers and compare the answers, in CI on every change to the code.
- Clients: end-to-end tests drive the official web vault and the Bitwarden CLI, with the clients' own cryptography, against Kennword and against Vaultwarden (docs/clients.md).
- Data: CI lets Vaultwarden fill an installation, moves it to Kennword and back on SQLite, MySQL and PostgreSQL, and compares what the clients read after each move.
- Code: internal reviews against Vaultwarden's source found and fixed vulnerabilities
(security review). PHPStan runs at its strictest level, and
composer auditin every CI run.
What is open
- No independent audit. It is the condition for version 1.0; when it happens has not been decided yet.
- Kennword is young (its first release was in October 2026), and its code was written with an AI coding assistant. The internal reviews were made with one too, and each of them found vulnerabilities, so more may remain.
Running it with care
- Back up the database and the
datafolder regularly and before every update (Backups), and try a restore once. - Keep the way back open: Kennword writes Vaultwarden's database and data folder in Vaultwarden's own formats. If Kennword lets you down, stop it and start Vaultwarden on the same data; the clients stay logged in (Going back).
- Coming from Vaultwarden, try Kennword on a copy of your data first; a new installation can start with a few users.
- Watch the repository's releases and security advisories: only the latest release gets fixes.
If your rules ask for an independently audited server, Kennword does not meet them yet.
Requirements
- PHP 8.5.12 or newer with the
openssl,sodiumandmbstringextensions andpdo_sqlite,pdo_mysqlorpdo_pgsqlfor the database; website icons also needxmlreaderandzlib, which PHP usually has - SQLite, MySQL/MariaDB or PostgreSQL
- A web server that passes requests to PHP (Apache, nginx, Caddy, ...) and serves HTTPS
Getting started
To try it locally, let Composer install it into a new folder:
That is the latest release; add dev-main
for the current state of main.
This installs the dependencies, creates .env and the application key, creates the database (SQLite at
data/db.sqlite3 by default) and downloads the web vault that Vaultwarden ships. In a Git checkout,
composer setup does the same. Then start PHP's built-in server and open http://127.0.0.1:8000, or
point a Bitwarden client at it:
Hosts without Composer get everything from a release archive instead: the code with its dependencies and the web vault, ready to upload (Installing from a release archive).
For a real installation, read the documentation:
- Installation: with Composer or from a release archive, web server, PHP settings, updates
- Configuration: Vaultwarden's settings and where Kennword differs
- Single sign-on: setting up Microsoft Entra ID, Keycloak or Google Workspace
- Moving from Vaultwarden: taking over an existing database and data folder, and going back
- Security review: what was reviewed, found and fixed, and what is open
Reporting problems
Please report problems with Kennword in this repository's issues, not to Vaultwarden: its maintainers have nothing to do with this port. Security issues go through the private channel described in SECURITY.md.
Contributing
See AGENTS.md describes the commands, the parity workflow and the conventions of the code, docs/clients.md the tests with the official clients, and docs/maintenance.md how advisories and Vaultwarden's changes are followed.
Credits
Kennword exists because of the work of others. NOTICE.md lists all of it in detail:
- Vaultwarden by Daniel García and the Vaultwarden contributors (AGPL-3.0): the behaviour Kennword ports, its database migrations, templates and domain lists, and the reference every test compares against.
- Bitwarden by Bitwarden, Inc.: the server whose API Vaultwarden reimplements (AGPL-3.0), and the clients Kennword serves (GPL-3.0).
- Rocket (MIT), whose default error pages Kennword copies, and the Rust crates whose behaviour it reproduces, among them Diesel, serde_json, chrono, jsonwebtoken, lettre, handlebars, webauthn-rs, openidconnect and oauth2.
- scssphp (MIT), which compiles the web vault's style changes as grass does in Vaultwarden.
- Laravel (MIT) and the PHP packages it runs on.
Every commit so far was written with Claude Code, Anthropic's AI
coding assistant; the commits say so in a Co-Authored-By trailer.
License
Copyright (C) 2026 Lumundi Versand GmbH and the Kennword contributors.
Kennword is free software under the GNU Affero General Public License, version 3 (AGPL-3.0-only), like Vaultwarden. If you run a modified version for others, the AGPL asks you to offer them its source code.
Bitwarden is a trademark of Bitwarden, Inc. Kennword is not affiliated with, associated with or endorsed by Bitwarden, Inc. or the Vaultwarden project.
All versions of vaultwarphpen with dependencies
devtheorem/php-handlebars Version ^2.2
laravel/framework Version ^13.17
laravel/tinker Version ^3.0
scssphp/scssphp Version ^2.1