paubox_rails 0.1.6 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ba84eed39a1ced7a4188e3b4d556e1eb0319af123cc42321bb13d07cadae126a
-  data.tar.gz: b146f6a504896c8c23a583de9ed7d0130b405aa07a8e6e20841a38aeff313f91
+  metadata.gz: efb96c5633f721a96323beab83ed91499817cc05e7e740da733d2ea3db907988
+  data.tar.gz: 766ce4809c4a6a74dee3c9614ec50407f8daa04351b00c6b5834126b1a9b7eb3
 SHA512:
-  metadata.gz: 13add0018eaa4d54876b6ad7c34f99eb6929e1586a2f9bc0dea605ec8ba965f0b6ab9935b622c5ecbc68f196849dabf14978aeae3bcd9a7d429d7e35ad9354d9
-  data.tar.gz: d7b3839e27cd935f360dc5d919f68e2e0ea9820db93bceb003f90d1f9ffaca47494a938c3d954ae67e785d553f4e7aba4284f156ac7d630d012fa23bd60478b1
+  metadata.gz: bd37d1a222575dafaae87e3afd92fe5dd54874778c1dff2ec2ae00a78ad42278873e509d3ec00eeb5616416434d7a74f6cd25593e1f472dc565bb9d33c805e83
+  data.tar.gz: bb9f9c170c09bb5aa043db76acdece25fb1a4bf089f11b2e3ecde245408ea88663718e8e2480b4befd1d7c892a7c9b1507567efda15ead0d6febe5a7d3752a60

data/.github/scripts/assert_specs_ran.rb

@@ -0,0 +1,40 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+# Fail CI when a green rspec exit code does not mean the suite ran.
+#
+# A passing run is not evidence of coverage: an error outside an example, a
+# stray tag filter, or a spec_helper that stops loading files can leave rspec
+# reporting success having executed almost nothing. The failure mode is
+# invisible precisely because the exit code is 0.
+
+require 'json'
+
+# Floor, not a target. Only trips if coverage regresses; adding specs is free.
+MIN_EXAMPLES = 120
+
+summary = JSON.parse(File.read(ARGV.fetch(0))).fetch('summary')
+
+total    = summary.fetch('example_count')
+pending  = summary.fetch('pending_count')
+failures = summary.fetch('failure_count')
+errors   = summary.fetch('errors_outside_of_examples_count')
+executed = total - pending
+
+puts format(
+  'examples=%d executed=%d failures=%d pending=%d errors_outside_examples=%d',
+  total, executed, failures, pending, errors
+)
+
+problems = []
+problems << "#{errors} error(s) outside of examples" if errors.positive?
+if executed < MIN_EXAMPLES
+  problems << "only #{executed} example(s) executed, expected at least #{MIN_EXAMPLES}"
+end
+
+unless problems.empty?
+  warn "FAIL: #{problems.join('; ')}"
+  exit 1
+end
+
+puts "OK: suite executed #{executed} examples"

data/.github/workflows/ci.yml

@@ -0,0 +1,42 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches: [master]
+
+permissions:
+  contents: read
+
+jobs:
+  spec:
+    name: rspec (ruby ${{ matrix.ruby }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        # 3.4 was excluded while the published paubox gem required base64
+        # without declaring it, which fails to load on 3.4 since base64 left
+        # the default gems there. paubox 1.0.0 declares base64 and ostruct, and
+        # this gem now requires '~> 1.0', so 3.4 is back.
+        ruby: ["3.1", "3.2", "3.3", "3.4"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          bundler-cache: true
+
+      - name: Run specs
+        # Both formatters are explicit: a CLI --format overrides the one in
+        # .rspec, so without this the log would be empty on failure. The JSON
+        # file feeds the gate below.
+        run: >-
+          bundle exec rspec
+          --format documentation
+          --format json --out rspec-results.json
+
+      - name: Assert the suite actually executed
+        run: ruby .github/scripts/assert_specs_ran.rb rspec-results.json

data/.github/workflows/pr-title.yml

@@ -0,0 +1,36 @@
+name: PR Title
+
+on:
+  pull_request:
+    branches: [master, main]
+    types: [opened, edited, reopened, synchronize]
+
+permissions:
+  contents: read
+
+jobs:
+  conventional-title:
+    name: Conventional commit title
+    runs-on: ubuntu-latest
+    steps:
+      # With squash merging the squash commit subject is the PR title, so this
+      # string is all release-please ever parses. A title it cannot parse is
+      # silently dropped from the release rather than failing anything, so it is
+      # gated here instead.
+      - uses: amannn/action-semantic-pull-request@v6
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          types: |
+            feat
+            fix
+            perf
+            revert
+            docs
+            style
+            refactor
+            test
+            build
+            ci
+            chore
+            deps

data/.github/workflows/release-please.yml

@@ -0,0 +1,88 @@
+name: release-please
+
+on:
+  push:
+    branches: [master]
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    name: Release Please
+    runs-on: ubuntu-latest
+    outputs:
+      release_created: ${{ steps.release.outputs.release_created }}
+      tag_name: ${{ steps.release.outputs.tag_name }}
+    steps:
+      # Maintains a release PR that bumps VERSION in
+      # lib/paubox_rails/version.rb and writes CHANGELOG.md. Merging that PR
+      # creates the tag and the GitHub release, which gates the publish below.
+      #
+      # The manifest is seeded from RubyGems (0.1.6), not from version.rb, which
+      # had drifted to 0.3.0. Neither 0.2.0 nor 0.3.0 was ever pushed, so
+      # seeding from the repo would have skipped two unused numbers.
+      #
+      # include-component-in-tag is false so tags stay bare `vX.Y.Z`, matching
+      # v0.1.6 and the rest of the SDK fleet.
+      - uses: googleapis/release-please-action@v4
+        id: release
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          config-file: release-please-config.json
+          manifest-file: .release-please-manifest.json
+
+  publish:
+    name: Publish ${{ needs.release-please.outputs.tag_name }} to RubyGems
+    needs: release-please
+    if: needs.release-please.outputs.release_created == 'true'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      # Required for OIDC. Without it the credentials step cannot identify
+      # itself to RubyGems.org and the push fails.
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ needs.release-please.outputs.tag_name }}
+          # The gemspec builds its file list from `git ls-files`, so the
+          # checkout has to keep the repository intact.
+          persist-credentials: false
+
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '3.4'
+          bundler-cache: true
+
+      - name: Run specs
+        run: bundle exec rspec --format documentation
+
+      - name: Verify the tag and version.rb agree
+        # Cheap guard against pushing a gem whose version does not match the
+        # tag it was cut from. RubyGems only allows a yank within 72 hours and
+        # never allows the number to be reused.
+        env:
+          RELEASE_TAG: ${{ needs.release-please.outputs.tag_name }}
+        run: |
+          GEM_VERSION=$(ruby -Ilib -e 'require "paubox_rails/version"; print PauboxRails::VERSION')
+          if [ "v${GEM_VERSION}" != "${RELEASE_TAG}" ]; then
+            echo "::error::version.rb is ${GEM_VERSION} but the tag is ${RELEASE_TAG}"
+            exit 1
+          fi
+          echo "version.rb ${GEM_VERSION} matches ${RELEASE_TAG}"
+
+      - name: Build the gem
+        run: gem build paubox_rails.gemspec
+
+      # Trusted publishing: exchanges GitHub's OIDC token for a short-lived
+      # RubyGems credential. There is no API key stored anywhere. RubyGems pins
+      # the trust to the repository and this workflow filename, so renaming
+      # this file breaks publishing until the trusted publisher entry for the
+      # `paubox_rails` gem is updated to match.
+      - name: Configure RubyGems credentials
+        uses: rubygems/configure-rubygems-credentials@main
+
+      - name: Push the gem
+        run: gem push paubox_rails-*.gem

data/.gitignore

@@ -10,4 +10,7 @@
 
 # rspec failure tracking
 .rspec_status
-*.gem
+*.gem
+
+# rspec JSON output written by CI.
+rspec-results.json

data/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "1.0.0"
+}

data/CHANGELOG.md

@@ -0,0 +1,69 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [1.0.0](https://github.com/Paubox/paubox-rails/compare/v0.1.6...v1.0.0) (2026-08-21)
+
+First stable release. RubyGems had been on `0.1.6` since September 2021.
+
+### ⚠ BREAKING CHANGES
+
+- Requires `paubox ~> 1.0` ([#17](https://github.com/Paubox/paubox-rails/pull/17)). The previous constraint was `~> 0.3`, which resolves to `< 1.0` and could not pick up [`paubox` 1.0.0](https://rubygems.org/gems/paubox/versions/1.0.0). Applications pinning `paubox` to a 0.x version must upgrade it alongside this gem
+
+### 🚀 New Features
+
+- Add `PauboxRails::Forms::Client` for the Paubox Forms API
+  - Public endpoints, no credential attached: `get_form`, `submit_form`
+  - Form management with a scoped API key (`forms` scope, read from `PAUBOX_FORMS_API_KEY` or passed to the constructor, sent as a Bearer token): `list_forms`, `create_form`, `get_form_details`, `update_form`, `archive_form`, `unarchive_form`, `copy_form`, `form_stats`
+  - Submissions: `list_submissions`, `submissions_csv`, `submission_pdf`
+- The Email API no longer requires a username — an API key alone authenticates
+
+### ⚠️ Behavior Changes
+
+- Base URLs move to `api.paubox.com`
+
+### 🔒 Hardening
+
+- Validate and encode caller-supplied values interpolated into Forms request paths. Authenticated endpoints require a UUID; public endpoints encode the segment instead of rejecting it
+
+### 🎉 Enhancements
+
+- Relicense from MIT to Apache 2.0, matching the rest of the Paubox SDKs
+- Replace the dead Travis config with a GitHub Actions CI workflow, now covering Ruby 3.1 through 3.4 ([51c3714](https://github.com/Paubox/paubox-rails/commit/51c3714d32bd2ed29c5c07a7a1d073719b58dbec))
+
+## v0.1.6 / 2021-09-27
+
+### 🎉 Enhancements
+
+- Remove the upper bound on the `actionmailer` dependency
+- Update the `rake` development dependency
+
+## v0.1.4 / 2019-07-10
+
+### 🎉 Enhancements
+
+- Require `paubox ~> 0.3`
+
+## v0.1.3 / 2018-10-04
+
+### 🎉 Enhancements
+
+- Widen the supported `actionmailer` range
+
+## v0.1.2 / 2018-10-04
+
+### 🎉 Enhancements
+
+- Require `paubox ~> 0.2`
+
+## v0.1.1 / 2018-07-25
+
+### 🎉 Enhancements
+
+- Constrain `actionmailer` to the versions then supported
+
+## v0.1.0 / 2018-04-26
+
+### 🚀 Major Release
+
+First release of the Paubox Transactional Email adapter for ActionMailer.

data/CLAUDE.md

@@ -0,0 +1,93 @@
+# CLAUDE.md — paubox-rails codebase guide
+
+## What this gem does
+
+`paubox-rails` is a thin Rails adapter gem with two responsibilities:
+
+1. **Email delivery** — Registers `:paubox` as an ActionMailer delivery method, delegating all sending to the [`paubox`](https://github.com/paubox/paubox_ruby) gem (`Mail::Paubox`).
+2. **Forms API client** — Provides `PauboxRails::Forms::Client` for interacting with the Paubox Forms API: public respondent endpoints (`get_form`, `submit_form` — no auth) plus authenticated form-management endpoints (list/create/update/archive/copy forms, stats, submissions, CSV/PDF export) that require a scoped API key with the `forms` scope, sent as `Authorization: Bearer`.
+
+## Key files
+
+```
+lib/
+  paubox_rails.rb               # Entry point: requires all components, registers delivery method
+  paubox_rails/
+    version.rb                  # VERSION constant
+    railtie.rb                  # Rails hook — registers delivery method before ActionMailer boots
+    forms.rb                    # PauboxRails::Forms module: BASE_URL, error classes, .client factory
+    forms/
+      client.rb                 # Forms HTTP client (Net::HTTP, no extra deps)
+spec/
+  paubox_rails_spec.rb          # Integration tests for ActionMailer delivery
+  paubox_rails/
+    forms/
+      client_spec.rb            # Unit tests for Forms::Client (Net::HTTP stubs)
+  fixtures/
+    models/test_mailer.rb       # Minimal ActionMailer subclass used in tests
+    views/test_mailer/          # ERB template for the test mailer
+```
+
+## Architecture
+
+```
+paubox-rails
+├── Email path
+│   ActionMailer → Mail::Paubox (from paubox gem) → RestClient → api.paubox.com
+└── Forms path
+    PauboxRails::Forms::Client → Net::HTTP → api.paubox.com/forms
+```
+
+- Email credentials (`api_key`) are configured via `Paubox.configure`.
+- Forms **respondent endpoints** (`get_form`, `submit_form`) are public — no credentials needed. All other Forms endpoints require a scoped API key (`forms` scope), passed via `Forms.client(api_key: ...)` or the `PAUBOX_FORMS_API_KEY` env var.
+
+## Running tests
+
+```bash
+bundle install
+bundle exec rspec
+```
+
+## How to add a new Forms endpoint
+
+1. Add a method to `lib/paubox_rails/forms/client.rb` following the `get_form` / `submit_form` pattern.
+2. Use `build_http(uri)` to get an SSL-ready `Net::HTTP` instance.
+3. Call `handle_response(response)` for consistent error handling.
+4. Add corresponding tests in `spec/paubox_rails/forms/client_spec.rb`, stubbing `Net::HTTP.new` via `instance_double`.
+5. Document the new method in `api.md` and `README.md`.
+
+## How to add a new email feature
+
+Email functionality lives in the `paubox` gem (not here). This gem only bridges ActionMailer to `Mail::Paubox`. To add email features, update the `paubox` gem and bump its version constraint in `paubox_rails.gemspec`.
+
+## Version
+
+Current: `0.3.0` (in `lib/paubox_rails/version.rb`)
+
+- `0.1.x` — Initial releases, email delivery only
+- `0.2.0` — Added Paubox Forms API support (public respondent endpoints)
+- `0.3.0` — Full Forms API support, including scoped-API-key (authenticated) management endpoints
+
+## Releases
+
+Releases are automated with [release-please](https://github.com/googleapis/release-please). Merging to `master` refreshes a standing release PR; merging *that* PR bumps `lib/paubox_rails/version.rb`, writes `CHANGELOG.md`, creates a bare `vX.Y.Z` tag and a GitHub release, and then **pushes the gem to RubyGems**.
+
+Do **not** hand-edit `VERSION` or add a `CHANGELOG.md` entry — release-please owns both.
+
+The next version comes from PR titles: `feat:` gives a minor bump, `fix:` a patch, and a `!` suffix or a `BREAKING CHANGE:` footer gives a major. `.github/workflows/pr-title.yml` rejects titles release-please cannot parse.
+
+To force a specific version, land an empty commit with a `Release-As` footer. Put the notes in the subject and footers — release-please renders those but not the commit body:
+
+```bash
+git commit --allow-empty -m "chore: release 1.0.0" -m "Release-As: 1.0.0"
+```
+
+### Publishing
+
+Publishing uses RubyGems **trusted publishing** (OIDC) — no API key is stored. RubyGems pins the trust to the repository and the workflow filename, so **renaming `release-please.yml` breaks publishing** until the trusted publisher entry for the `paubox_rails` gem is updated.
+
+Version numbers on RubyGems are effectively permanent — a yank is only possible within 72 hours and never frees the number for reuse.
+
+### Relationship to the `paubox` gem
+
+This gem depends on `paubox` and the gemspec constraint has to allow whatever major version is current there. When `paubox` takes a major bump, this gem needs a matching release that widens the constraint — otherwise Bundler silently holds users on the older `paubox` with no error. Release `paubox` first, then this gem.

data/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may accept and charge a
+      fee for, acceptance of support, warranty, indemnity, or other
+      liability obligations and/or rights consistent with this License.
+      However, in accepting such obligations, You may act only on Your
+      own behalf and on Your sole responsibility, not on behalf of any
+      other Contributor, and only if You agree to indemnify, defend,
+      and hold each Contributor harmless for any liability incurred by,
+      or claims asserted against, such Contributor by reason of your
+      accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Paubox, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.