Learn how Passbolt and PearPass differ in their key features, development activity, technology stack and community adoption, so you can decide which of these password managers is best for you.
Last 30 days
Last commit
19 days agoRepository age
11 yearsVersion
v5.17.0License
AGPL-3.0Self-hosted
YesRepository
passbolt_api
Last 30 days
Last commit
3 months agoRepository age
11 monthsVersion
v2.1.0License
Apache-2.0Repository
pearpass-app-desktop
Passbolt appears to have several advantages over PearPass, particularly in popularity, growth, activity, maturity and features. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Passbolt significantly outpaces PearPass in community adoption with 6,217 stars compared to 543 stars on GitHub. This 11.4x difference suggests Passbolt has a much larger and more active community. In terms of developer contributions, Passbolt has 405 forks, indicating moderate developer engagement.
Passbolt is growing faster, adding 67 stars in the last 30 days (+1.1%) against adding 4 stars for PearPass (+0.7%). Passbolt is both larger and pulling further ahead.
Passbolt shows more recent development activity with its last commit 19 days ago, while PearPass was last updated 3 months ago. This suggests Passbolt is being more actively maintained.
Both tools share common technology foundations, being built with JavaScript, Bash. However, they differ in their additional technology choices: Passbolt uses CSS, PHP while PearPass leverages Typescript, JSX.
Passbolt has been in development longer, starting 11 years ago, compared to PearPass which began 11 months ago. This 9.9-year head start suggests Passbolt may have more mature features and established processes.
The projects use different licenses: Passbolt is licensed under AGPL-3.0 while PearPass uses Apache-2.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Password Managers.
Passbolt provides self-hosting options for complete data control and customization, while PearPass may be primarily cloud-based or require different deployment approaches.