Frappe Mail

End-to-End Email Management Platform

Frappe Mail is a generic JMAP client and an orchestration layer designed to deploy and manage Stalwart Mail clusters. It supports multi-tenancy and multi-cluster setups, where each tenant manages its own domains, members, and configurations, and must be assigned to a specific cluster. Frappe Mail handles provisioning, configuration, synchronization, and lifecycle operations across clusters, while exposing a unified interface for applications.

• Introduction
  • Overview
• Getting Started
  • Installation and Setup
• APIs
  • Auth
  • Outbound
  • Inbound
• Frontend UI
  • Mailbox
  • Admin Dashboard
  • Sign-up Flow
• Contributing
• License

Frappe Mail is an end-to-end email management platform built on the Frappe Framework. It combines a fully compliant JMAP client with a powerful orchestration layer for deploying, configuring, and managing Stalwart Mail clusters. Whether you are connecting to an existing JMAP-compatible mailbox, self-hosting for your organization, or running a multi-tenant email service, Frappe Mail provides a unified interface for provisioning, automation, monitoring, and day-to-day email operations.

At its core, Frappe Mail serves two major roles:

1. A Generic JMAP Client

It offers a modern, standards-compliant interface for sending, receiving, and managing email. Any mailbox hosted on a JMAP-compatible provider—such as Stalwart Mail or FastMail—can be accessed through Frappe Mail’s UI and APIs.

2. A Multi-Cluster Orchestration Layer for Stalwart Mail

Frappe Mail can deploy and manage one or many Stalwart Mail clusters. It provisions servers, configures storage backends, manages TLS, syncs tenant/domain/account settings, and exposes lifecycle operations through a unified control plane.

With multi-tenant and multi-cluster support, each tenant operates its own domains, mailboxes, and configurations, while the system ensures consistent provisioning and synchronization across all connected Stalwart nodes.

This makes Frappe Mail suitable for:

• organizations self-hosting their email infrastructure,
• companies offering email as a service,
• developers integrating a JMAP-first mail system into their applications,
• or teams simply looking for a unified admin and client interface over existing Stalwart clusters.

This section will help you set up and configure Frappe Mail, ensuring that your email system is ready to use. It includes instructions for installing both the Stalwart Mail Server and the Frappe Mail app, details about system requirements, and steps for the initial configuration.

Follow these steps to install and set up Frappe Mail and its supporting components:

The first step is to install the Frappe Mail app. You can choose between using Docker for an easy setup or performing a manual installation.

Using Docker

1. Download the docker-compose.yml file:

   wget -O docker-compose.yml https://raw.githubusercontent.com/frappe/mail/develop/docker/docker-compose.yml

2. Download the setup script:

   wget -O init.sh https://raw.githubusercontent.com/frappe/mail/develop/docker/init.sh

3. Run the container in detached mode:

   docker compose up -d

4. Access the Frappe Mail site: Visit http://mail.localhost in your browser.

   Default Credentials:

   • Username: administrator
   • Password: admin

Manual Installation

1. Prerequisite: Ensure that the Frappe Bench is installed and running on your system. If not, refer to the Frappe installation guide for detailed steps.

2. Install the Mail App and Create a Site: Run the following commands to install the Mail app and set up a new Frappe site:

     bench get-app mail
     bench new-site mail.localhost --install-app mail
     bench browse mail.localhost --user Administrator

The Stalwart Mail Server acts as the backbone of Frappe Mail’s infrastructure. Below is an improved, structured guide for setting up Stalwart for both development and production.

1.1 Set Root Domain Name

• Open Mail Settings and set the Root Domain Name.
• This domain is used for DNS configurations such as the root SPF record.
• If you are offering Frappe Mail as an email service provider, set this to your primary domain (e.g., frappemail.com, gmail.com).
• For organizational use, set it to your company’s domain.

1.2 Configure DNS Provider (Optional)

• If your DNS provider is supported, enable its integration in Mail Settings.
• When enabled, DNS records for Mail Clusters and Mail Servers will be updated automatically.
• If unsupported, you must manually create DNS records.

Supported DNS Providers: Route53, DigitalOcean, Cloudflare, Hetzner, Linode, Namecheap, GoDaddy.

This step walks you through creating a Mail Cluster and deploying one or more Mail Servers.

2.1 Create a Mail Cluster

• Go to Mail Cluster → New.
• Hostname: FQDN of your reverse proxy or load balancer. For single‑server setups, the Mail Cluster and Mail Server hostname can be the same.
• Base URL: JMAP endpoint URL. If using a reverse proxy or non‑default port, include it here.
• Storage:
  • Development / single‑server: Default RocksDB for all storage layers.
  • Production / multi‑server: Prefer distributed backends:
    • Directory & Data: Distributed DB
    • Blob: S3 or compatible storage
    • Full‑Text Search: ElasticSearch
    • In‑Memory: Redis
• Logs & Metrics: Enable and configure Prometheus or OpenTelemetry if needed.

2.2 Create a Mail Server

• Go to Mail Server → New.
• Select the previously created Mail Cluster.
• Hostname: FQDN of this specific server (or same as cluster for single‑server deployments).
• Node ID: Sequential numbers (1, 2, 3...) for each server in the cluster.
• Save the Mail Server.

2.3 Verify SSH Access

After saving the Mail Server:

1. Open the SSH tab in the Mail Server document.
2. Copy the auto-generated public SSH key.
3. Add the key to your server’s ~/.ssh/authorized_keys file.
4. Click Actions → Verify SSH Connection.

When verified, extra actions become available:

• Install Ansible (track progress via Server Job document)
• Install Docker (track progress via Server Ansible Play document)
• Install Stalwart (track progress via Server Deployment document)

2.4 Configure HTTPS / TLS (Production)

For production environments, HTTPS/TLS is strongly recommended.

Option A: Use ACME (Recommended)

• Configure an ACME Provider in the Mail Server.
• Ensure your domain’s DNS records point to the server before proceeding.
• Example: mail.example.com → A record → Server IP.

Option B: Use Existing TLS Certificates

1. Copy your TLS certificate and private key to the server.

2. Add a new entry in the TLS Certificates table with:

   • Certificate Path
   • Private Key Path
   • Subject Alternative Names

3. Ensure the Stalwart process has read permissions for both files.

2.5 Generate and Deploy Server Configuration

Whenever you make changes to a Mail Cluster or Mail Server, you must regenerate and deploy the server configuration.

1. In the Mail Server document, click Actions → Generate Config.

2. Deploy the updated configuration using one of the following options:

   • Actions → Install Stalwart

     • Installs Stalwart and always uses the latest generated configuration.

   • Server Config → Actions → Deploy

     • Deploys Stalwart using a specific configuration version.

2.6 Access the Stalwart Admin Panel After installation completes:

• Open the Stalwart Admin Panel in your browser.
• Log in using the admin credentials defined in the Mail Cluster document.

• During Mail app installation, a default tenant named "Frappe Mail" is created.
• Each tenant must be assigned a Mail Cluster.
• Open the tenant → set the Mail Cluster created earlier.

4.1 Create a Mail Domain Request

• Go to Mail Domain Request → New.
• After saving, a Verification Key (TXT record) is generated.
• Add this TXT record to your domain’s DNS settings.
• If the domain matches the Root Domain and your DNS provider is integrated, you can auto‑create this record via a DNS Record document.

4.2 Verify and Create Domain

• Once the DNS TXT record is applied, click Actions → Verify and Create Domain.

• Upon successful verification:

  1. The domain is created on the Stalwart Mail Server. You will now see the required DNS records (SPF, DKIM, DMARC, MX, etc.) that must be added to your DNS provider to ensure proper email deliverability and prevent spoofing.

  

  2. A domain–tenant binding is created. This links the domain to the tenant for management and provisioning.

  

4.3 Development Mode (Optional)

If you're working in a development environment and cannot verify DNS records, you may manually check the Verified checkbox and save the document to bypass verification.

Repeat the above process to add additional domains.

• Create a Mail Account Request.

  

• Email: Used for invitations and password resets.

• Account: The mailbox address; used to create the User document and login to the Mail UI.

• Enable Send Invite if you want to send an onboarding email. Ensure you have a default Email Account configured for outbound mail.

  

After saving:

• The user receives a verification link, or
• You may use Force Verify to immediately create the account.

• Endpoint: POST /auth/validate or /api/method/mail.api.auth.validate
• Description: Validates if a user has the required permissions and owns the email address.
• Parameters:
  • email (str): The email address to validate.
• Response: Returns nothing if validation is successful. Throws an exception with the reason if the email address cannot be validated.

APIs for sending emails through Frappe Mail.

• Endpoint: POST /outbound/send or /api/method/mail.api.outbound.send
• Description: Sends an email message with options for attachments, carbon copies (cc), and blind carbon copies (bcc).
• Parameters:
  • from_ (str): The sender's email address.
  • to (str | list[str]): Recipient email(s).
  • subject (str): Subject of the email.
  • cc (str | list[str] | None): Optional carbon copy recipients.
  • bcc (str | list[str] | None): Optional blind carbon copy recipients.
  • html (str | None): Optional HTML body of the email.
  • reply_to (str | list[str] | None): Optional reply-to email(s).
  • in_reply_to_mail_type (str | None): Optional reference type for the email being replied to.
  • in_reply_to_mail_name (str | None): Optional reference ID for the email being replied to.
  • custom_headers (dict | None): Optional custom headers.
  • attachments (list[dict] | None): List of attachments.
  • is_newsletter (bool): Optional flag to mark the email as a newsletter. Defaults to False.
• Response: Returns a UUID (name) of the created Mail Queue document.
• Example Response:

  { "message": "019300a4-91fc-741f-9fe5-9ade8976637f" }

• Endpoint: POST /outbound/send-raw or /api/method/mail.api.outbound.send_raw
• Description: Sends a raw MIME message. This can be useful for users who want to send a preformatted email.
• Parameters:
  • from_ (str): Sender's email address.
  • to (str | list[str]): Recipient email(s).
  • raw_message (str): The complete raw MIME message.
  • is_newsletter (bool): Optional flag to mark the email as a newsletter. Defaults to False.
• Response: Returns a UUID (name) of the created Mail Queue document.
• Example Response:

  { "message": "019300a4-91fc-741f-9fe5-9ade8976637f" }

APIs for retrieving emails.

• Endpoint: GET /inbound/pull or /api/method/mail.api.inbound.pull
• Description: Fetches a list of emails (details).
• Parameters:
  • mailbox (str | None): The mailbox to fetch emails from. Defaults to inbox.
  • limit (int = 50): Maximum number of emails to retrieve.
  • last_received_at (str | None): Optional timestamp to fetch emails received after this time.
• Response: Returns a dictionary with a list of email details.
• Example Response:

{
  "message": {
    "mails": [
      {
        "user": "[email protected]",
        "sent_at": "2025-12-08 12:51:09+00:00",
        "id": "bfqaaaaj3",
        "size": 5243,
        "received_at": "2025-12-08 12:51:10+00:00",
        "blob_id": "ccodqfu9bg1aevchbuyrlcpprhctnqq9ao2h3gkbdy1zysoseq33qpaax2ba",
        "subject": "Hello \ud83d\udc4b",
        "thread_id": "jm",
        "name": "[email protected]|bfqaaaaj3",
        "preview": "Hello, From Frappe Mail...",
        "has_attachment": 0,
        "keywords": "{\n    \"$seen\": true\n}",
        "received_after": 1.0,
        "sender_name": null,
        "sender_email": null,
        "from_name": "Sagar Sharma",
        "from_email": "[email protected]",
        "reply_to": [],
        "recipients": [
          {
            "type": "To",
            "display_name": null,
            "email": "[email protected]"
          }
        ],
        "html_body": "<div>Hello, From Frappe Mail\u2026</div>",
        "text_body": "Hello, From Frappe Mail...",
        "mailboxes": [
          {
            "mailbox": "[email protected]|a",
            "mailbox_id": "a",
            "mailbox_name": "Inbox"
          }
        ],
        "draft": 0,
        "junk": 0,
        "seen": 1,
        "flagged": 0,
        "answered": 0,
        "forwarded": 0,
        "message_id": "[email protected]",
        "in_reply_to": null,
        "attachments": [],
        "_html_body": [
          {
            "part_id": "2",
            "blob_id": "ckodqfu9bg1aevchbuyrlcpprhctnqq9ao2h3gkbdy1zysoseq33qpaax2bjmkbl",
            "size": 37,
            "filename": null,
            "type": "text/html",
            "charset": "utf-8",
            "disposition": null,
            "cid": null,
            "language": "None",
            "location": null
          }
        ],
        "_text_body": [
          {
            "part_id": "1",
            "blob_id": "cgodqfu9bg1aevchbuyrlcpprhctnqq9ao2h3gkbdy1zysoseq33qpaax2bowjq7",
            "size": 26,
            "filename": null,
            "type": "text/plain",
            "charset": "utf-8",
            "disposition": null,
            "cid": null,
            "language": "None",
            "location": null
          }
        ]
      }
    ],
    "last_received_at": "2025-12-08 12:51:10+00:00",
    "last_received_mail": "[email protected]|bfqaaaaj3"
  }
}

• Endpoint: GET /inbound/pull-raw or /api/method/mail.api.inbound.pull_raw
• Description: Fetches a list of emails (raw).
• Parameters: Same as /inbound/pull.
• Response: Returns raw MIME messages.
• Example Response:

  {
    "message": {
      "mails": [
        "Delivered-To: [email protected]\r\nReceived: from outbound.frappemail.com (outbound.frappemail.com [13.232.52.137] (AS16509 Amazon.com, Inc., IN))\r\n\t(using TLSv1.3 with cipher TLS13_AES_256_GCM_SHA384)\r\n\tby inbound.frappemail.com (Stalwart SMTP) with ESMTPS id 3DE517AF3D36E02;\r\n\tMon, 8 Dec 2025 12:51:09 +0000\r\nAuthentication-Results: inbound.frappemail.com;\r\n\tdkim=pass header.d=frappe.io header.s=frappemail-r header.b=EmGbuDcw;\r\n\tspf=pass (inbound.frappemail.com: domain of [email protected] designates 13.232.52.137 as permitted sender) smtp.helo=outbound.frappemail.com;\r\n\tspf=pass (inbound.frappemail.com: domain of [email protected] designates 13.232.52.137 as permitted sender) [email protected];\r\n\tiprev=pass policy.iprev=13.232.52.137;\r\n\tdmarc=pass header.from=frappe.io policy.dmarc=none\r\nReceived-SPF: pass (inbound.frappemail.com: domain of [email protected] designates 13.232.52.137 as permitted sender)\r\n\treceiver=inbound.frappemail.com; client-ip=13.232.52.137; envelope-from=\"[email protected]\"; helo=outbound.frappemail.com;\r\nARC-Seal: i=1; a=rsa-sha256; s=frappemail-r; d=frappemail.com; cv=none;\r\n\tb=nYEPel+3YDOZLQWFY8EjRetymxtxfAz8K+BABOzTBUF9rGsjo99ILbsDwExo+9o1rpm/wHekh\r\n\tEUumEVVqAk9cX16CpzpMy6T+SahqyfZA1ywPZcTxXoDcBbn3Hs5LF5DeHewYPBE920EWijGXcf1\r\n\tL/AvyqEor10cL+6iYcLzkg4/gjVp7jwWitBfGTu9tBSuITYeK4YKh6zUsLDn5O/VCsS96j6Bfss\r\n\ttAGNYNPzALsLEMSMsSZBHhqsC93z8nFEFZIt9834x2UjmSQPCeYcnDSP5IVY5LaYSbM4wEt2Y+k\r\n\tMyLCz7Aa4X4hSJZdFZ+s4BB7pS9drvegGw/BzY+Svkfw==;\r\nARC-Message-Signature: i=1; a=rsa-sha256; s=frappemail-r; d=frappemail.com; c=relaxed/relaxed;\r\n\th=Message-ID:Date:Subject:To:From:DKIM-Signature; t=1765198269; bh=HU/S44HL\r\n\tsW+Js8pc9uxS0io7t8u6R4AN0oaeXnEotTY=; b=qIFx/XH2QIv69i98admlzL5Uj0q7Jr2Q2aw\r\n\tigLKuUsjn7UKqpESiKgKLP/S2xMvt/wtQ6BvgENBEcbrUPAznnmS7rOErj7iptHAvaCVVWoHuSd\r\n\ttHLdntULe+2lK4+Td6Zos05KegkbQWGiMSjaK8trxSEZBapv87aSWcUUIZSVAhRIcXK4a5vhF0l\r\n\tQiDAAOxT5hyPOsoC4mxzceXHM7PAT477OBFBxFERoqtT9bcJR+eqoDrdcCMiWBoU0sBm/wnN/KS\r\n\tfK+m78KQruROrrRg2NgbbXDC0OhtN873ifGNF44Dviia2qgZnzSJZlGL0dhn68aBLRN0BbvQkR6\r\n\tz4zawRA==;\r\nARC-Authentication-Results: i=1; inbound.frappemail.com;\r\n\tdkim=pass header.d=frappe.io header.s=frappemail-r header.b=EmGbuDcw;\r\n\tspf=pass (inbound.frappemail.com: domain of [email protected] designates 13.232.52.137 as permitted sender) smtp.helo=outbound.frappemail.com;\r\n\tspf=pass (inbound.frappemail.com: domain of [email protected] designates 13.232.52.137 as permitted sender) [email protected];\r\n\tiprev=pass policy.iprev=13.232.52.137;\r\n\tdmarc=pass header.from=frappe.io policy.dmarc=none\r\nX-Spam-Result: TRUSTED_DOMAIN (-7.00),\r\n\tDMARC_POLICY_ALLOW (-0.50),\r\n\tDKIM_ALLOW (-0.20),\r\n\tSPF_ALLOW (-0.20),\r\n\tARC_NA (0.00),\r\n\tDBL_BLOCKED_OPENRESOLVER (0.00),\r\n\tDKIM_SIGNED (0.00),\r\n\tFROM_EQ_ENV_FROM (0.00),\r\n\tFROM_HAS_DN (0.00),\r\n\tHTML_SHORT_1 (0.00),\r\n\tMID_RHS_MATCH_ENV_FROM (0.00),\r\n\tRBL_SENDERSCORE_REPUT_BLOCKED (0.00),\r\n\tRBL_SPAMHAUS_BLOCKED_OPENRESOLVER (0.00),\r\n\tRCPT_COUNT_ONE (0.00),\r\n\tRCVD_TLS_LAST (0.00),\r\n\tTO_DN_NONE (0.00),\r\n\tTO_MATCH_ENVRCPT_ALL (0.00),\r\n\tXM_UA_NO_VERSION (0.01),\r\n\tRCVD_COUNT_ZERO (0.10),\r\n\tMID_RHS_MATCH_FROM (1.00),\r\n\tDIRECT_TO_MX (2.00)\r\nX-Spam-Status: No, score=-4.79\r\nReturn-Path: <[email protected]>\r\nDKIM-Signature: v=1; a=rsa-sha256; s=frappemail-r; d=frappe.io; c=relaxed/relaxed; r=y;\r\n\th=Message-ID:Date:Subject:To:From; t=1765198270; bh=HU/S44HLsW+Js8pc9uxS0io\r\n\t7t8u6R4AN0oaeXnEotTY=; b=uxoGwis9QYH+P/IXCi2hEMHUTP8Y4v3XprDTK7YtW74ye0MZrq\r\n\tIYkUykR6upglHaH1SReQwnMq3SbTP3aRXD4j9JHdOhIONLUB85q7ld7Khw/nX7lBnJZzjQar0tQ\r\n\tgmZcDifHtLXhVg9j5CXEdYzl5MnXfVy8OFYW5qhmw/MxBpObP+6WcpdaGmMSuadjjCpfWbwq0hu\r\n\t5AAMtxxw1l/YdI6C3+kardnf50XBVrRaVcZOU5bN5W2uUfTIkOzjTO06HaqsKYRobhzyR2kQzU+\r\n\tGwbaksXPUEErHU547w58SOOqRb76oMI6q8iCwLs9apYcVhx3wwrBYNIeywM47gcuUJQ==;\r\nDKIM-Signature: v=1; a=rsa-sha256; s=frappemail-r; d=frappe.io; c=relaxed/relaxed; r=y;\r\n\th=Message-ID:Date:Subject:To:From; t=1765198269; bh=HU/S44HLsW+Js8pc9uxS0io\r\n\t7t8u6R4AN0oaeXnEotTY=; b=EmGbuDcwO/LTKiJAyMcxYv7qNl5MwEMQYfaKAMDXSV5CNW1dcf\r\n\tbMz/Ei/pIs+F2DWZtFmJJvKx8K1bAlV8ky0M/GXemoX09dBxZKn+ncBmdsP2E5hSZdj1smUZRRG\r\n\tgGiHje0msh0SK93nysiq0Fmb7C86wfXGTDwTanvBky7LFq4ijJR3QKVqaHJBlCOKpD3jl0h/8PA\r\n\tYEbD2ay9cmCMZPNPhTfFfEfjQCpo99UX9ocjWKmDeta8M312jyJ5rjmI0Nxj4jB9IxlQgN3Prng\r\n\tiCBZREA5FAO5ueFziF6lP11yW3EAh16fQ+Ty6ocWouuxCuYZ6VuAULiv/UlnTYexVCA==;\r\nFrom: \"Sagar Sharma\" <[email protected]>\r\nTo: <[email protected]>\r\nSubject: =?utf-8?B?SGVsbG8g8J+Riw==?=\r\nDate: Mon, 8 Dec 2025 12:51:09 +0000\r\nMessage-ID: <[email protected]>\r\nUser-Agent: Frappe Mail v0.0.1 (Frappe v16.0.0-dev)\r\nX-Mailer: Frappe Mail\r\nX-Mail-Queue: 019afe04-0aeb-7cd1-a3b6-5f93feddbedc\r\nMIME-Version: 1.0\r\nContent-Type: multipart/alternative; \r\n\tboundary=\"187f3e793201e2ca_b8edd88d54e943e0_a21106607a32b002\"\r\n\r\n\r\n--187f3e793201e2ca_b8edd88d54e943e0_a21106607a32b002\r\nContent-Type: text/plain; charset=\"utf-8\"\r\nContent-Transfer-Encoding: 7bit\r\n\r\nHello, From Frappe Mail...\r\n--187f3e793201e2ca_b8edd88d54e943e0_a21106607a32b002\r\nContent-Type: text/html; charset=\"utf-8\"\r\nContent-Transfer-Encoding: quoted-printable\r\n\r\n<div>Hello, From Frappe Mail=E2=80=A6</div>\r\n--187f3e793201e2ca_b8edd88d54e943e0_a21106607a32b002--\r\n"
      ],
      "last_received_at": "2025-12-08 12:51:10+00:00",
      "last_received_mail": "[email protected]|bfqaaaaj3"
    }
  }

Frappe Mail ships with its own frontend UI that can be broadly classified into two parts:

• Mailbox
• Admin Dashboard

The Mailbox is the primary user-facing area of Frappe Mail. This is where users spend most of their time reading, composing, and managing emails.

Some of its features include:

The Admin Dashboard is the administrative and configuration interface of Frappe Mail. It is designed for tenant administrators to manage accounts, domains, and tenant-wide settings.

Some of its features include:

Before accessing the Mailbox or Admin Dashboard, users complete a one-time sign-up and setup flow. Depending on the user and their requirements, Frappe Mail offers three types of sign-ups:

• Business Sign-up
• Personal Sign-up
• Invite-based Sign-up

For organizations setting up their own tenant, including custom domains, accounts, and organization-level configurations.

Note: This has to be enabled in Mail Settings

1. Go to /mail/signup and select 'Business (For work or company use)'

2. Enter your current email address

3. A verification email will be sent to this account

4. Copy the code and paste it into the Mail app, or click on 'Verify Account'

5. Enter your details

6. Enter the name of your orangization, and click on 'Create Organization'

A new tenant will be created with you as the tenant owner. Click on 'Add Domain' and follow the instructions on screen to set up your first domain and its corresponding members.

For allowing users to create an account with one of the domains whitelisted by a system administrator.

Note: This has to be enabled in Mail Settings

1. Go to /mail/signup and select 'Personal (For individual user)'

2. Enter your name

3. Enter a username and select one of the whitelisted domains

4. Enter a backup email address for recovery

4. Enter a password, and click on 'Sign Up'

The user will now have a mail account with the selected domain and user details on Frappe Mail.

For inviting external individuals to be members of your tenant.

1. Invite the member through the Admin Dashboard by assigning them an email address, and clicking on 'Invite Member'

2. The user will receive an email at the backup email address. Click on 'Verify Account'.

3. Fill out the details, and click on 'Create Account'

This will result in the creation of a new tenant account with the given details.

This app uses pre-commit for code formatting and linting. Please install pre-commit and enable it for this repository:

cd apps/mail
pre-commit install

Pre-commit is configured to use the following tools for checking and formatting your code:

• ruff
• eslint
• prettier
• pyupgrade

GNU Affero General Public License v3.0