passbolt/passbolt_api

Passbolt Community Edition (CE) API. The JSON API for the open source password manager for teams!

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 54 minutes ago
Added to GitGenius on September 11th, 2026
Created on February 23rd, 2016
Open Issues & Pull Requests: 26 (+0)
GitHub issues: Enabled
Number of forks: 399
Total Stargazers: 6,115 (+0)
Total Subscribers: 88 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.6 hours
Mean response time: 13.6 days
90th percentile: 64.2 days
Tracked items: 87

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 9% of issues opened in the past year have been closed. Three people close 73% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 321 days
Stale 30+ days: 14
Stale 90+ days: 12

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (15)
  • enhancement (10)
  • waiting for reporter feedback (6)
  • question (4)
  • invalid (3)
  • groomed (2)
  • help wanted (2)
  • requirements wanted (2)

Most active issues this week

Detailed Description

Passbolt is a JSON API for an open source password manager designed for teams.

The tool addresses the need for secure, collaborative credential management by providing a backend API that handles password storage, sharing, and access control across team members. It uses a client-server architecture where the API manages encryption, user authentication, and permission enforcement, allowing teams to securely store and distribute passwords without relying on a centralized service provider.

Teams evaluating Passbolt should understand that it is built on CakePHP and designed specifically for collaborative password management rather than individual use. It suits organizations that want to self-host their password infrastructure and maintain control over credential data. The project is positioned as a community edition, indicating that alternative commercial or enterprise versions may exist, though the README does not detail how they differ.

The project shows consistent development activity with regular commits across its codebase. Pull requests are reviewed and merged steadily, indicating ongoing maintenance and feature development. The issue tracker reflects active engagement with bug reports and feature requests from users. Documentation is maintained alongside code changes, suggesting the team prioritizes keeping guidance current with implementation.