@bitwarden/cli
A secure and free password manager for all of your devices.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Bitwarden migrated to GitHub Actions CI publishing; consistent with org-wide automation shift. | ai | |
| provenance | missing-githead | AI (provenance): Expected artifact of GitHub Actions publish pipeline change; not a supply-chain indicator for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Bitwarden package; absence of Sigstore attestation is not a risk signal here. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Bitwarden employees added as part of org-wide team expansion. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): kspearrin removal consistent with role change within Bitwarden org, not a takeover. | ai | |
| phantom-deps | phantom-dep:koa | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution, not direct imports. | ai | |
| phantom-deps | phantom-dep:lunr | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:open | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:jsdom | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:jszip | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:lowdb | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:tldts | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:multer | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:zxcvbn | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Bundled CLI; known implicit runtime polyfill dependency. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai | |
| phantom-deps | phantom-dep:koa-json | AI (phantom-deps): Bundled CLI; deps listed for webpack/pkg resolution. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2026.4.2 | 27 / 0 | |
| 2025.11.0 | 27 / 0 | |
| 2025.3.0 | 26 / 0 | |
| 2024.6.0 | 26 / 0 | |
| 2024.4.0 | 26 / 0 |
v2026.4.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2025.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2024.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2024.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.