Analyzed
32 minutes
ago.
based on code collected
about 2 hours
ago.
Project Summary
legacy-proxy is a translation layer that puts a JMAP for Mail server in front of a classic IMAP / SMTP / ManageSieve / CardDAV stack. It speaks RFC 8620 + RFC 8621 to clients, and standard mailbox protocols to whatever server already holds the user's mail. No new mail store, no migration: the mail keeps living in the existing IMAP server, and a modern JMAP client sees the account as if it were native.
In a Nutshell, legacy-proxy JMAP from IMAP...
- ...
- ...
-
...
has a codebase with a very short history
maintained by a small development team
with stable Y-O-Y commits -
...
took an estimated 3 years of effort (COCOMO model)
starting with its first commit in April, 2026
ending with its most recent commit 12 days ago
Quick Reference
https://github.com/bulwarkmail/l...
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Poor security track-record
Favorable security track-record
Vulnerability Exposure Index
Many reported vulnerabilities
Few reported vulnerabilities
Did You Know...
-
...
55% of companies leverage OSS for production infrastructure
-
...
anyone with an Open Hub account can update a project's tags
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
data presented on the Open Hub is available through our API
30 Day SummaryAug 27 2026 — Sep 26 2026
|
12 Month SummarySep 26 2025 — Sep 26 2026
|
