oauth 1.1.5 → 1.1.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7b6d26e7154c4142ab4895d3a3b5df7ec1f1db47c4b921262c815e3f2f59c67e
-  data.tar.gz: 44b919663b563b37a1ba49d7c07a0a452a13fb040948135de6f39065155f46c0
+  metadata.gz: 519d2a63b05220f02dadb8fcb8ba9cb20ce54f03c617b2a74e46781b9c0b843c
+  data.tar.gz: 8a89f0260d3b91eff46f969208d4baafd3122f86fea184c8380c72d0f8aed5bd
 SHA512:
-  metadata.gz: d0cee0dcba52b6bdfd864aef0ea81160e47e093ec8457d8d6a36799aab6951008979480725983edd4135c2aa1725b8b18ac3fe29879df93cf1f53cc8a942095c
-  data.tar.gz: 45fa31d073726e816937718f97038e803bbea92722936b88195038b2a42a5c6ebf540017e29e644efcba89e44f8e3ad3452ff6987823e8a9d5ad49ec5f4262c2
+  metadata.gz: 37c222e2be4fe2e4bac7615d794abf35a0f9750ab447b40654fab78b47f539c8a0bb4df17b520e90a8f998b3ea9dcda1ad6f0da97a123335f38d28fb94b17a7d
+  data.tar.gz: 98725428c6aab7b988766e9f4c65e6b6bb78ce0079c07ab5c65e8c1f65ebdeb11488cccfe94f31f78d6b77a164b60b20ea94dfc8b755b67261af4de04ed09772

checksums.yaml.gz.sig

@@ -1,4 +1 @@
-A�1a�1����Ztv*PQ�����Z�Ҫ�����(@��n���s��̍��@�q������6D�*�+�MF���.܇2a���A��͒W{]�l����S�֛�/Ry�DJhA#Sjz�o6pRM�	���6���������T����JH^'}z��鹽�����X��d�J�3�
-۲�OU*�9�s::rT���WXSD��F�_�X�H_�B�d��0ma�1ݾ��jUKz�Sҥ�m��=�qWǣ�]��,H��w��mp��8u�,s:��2��
�d>@�w
-���!-a|w��R�1�uo�,	e��a���=�:�0�D�����&}0����{v:'�sg�y�"~��H�y!���,H
-/�VG�,���J
+�V�T4�7��M�YS#m�π��o�?�K�.���-1�]F��x�,�s���!���I|��p�Ne��

data/CHANGELOG.md

@@ -30,6 +30,28 @@ Please file a bug if you notice a violation of semantic versioning.
 
 ### Security
 
+## [1.1.6] - 2026-06-07
+
+- TAG: [v1.1.6][1.1.6t]
+- COVERAGE: 89.05% -- 838/941 lines in 33 files
+- BRANCH COVERAGE: 60.46% -- 159/263 branches in 33 files
+- 40.38% documented
+
+### Changed
+
+- Retemplated project workflows, appraisals, and development tooling with the
+  current `kettle-jem` template.
+- Documented current `OAuth::Consumer` configuration options, including token
+  request redirect safety settings, and corrected the OAuth 1.0a usage example.
+- Raised the runtime dependency floor for `auth-sanitizer` to `>= 0.2.1`.
+- Raised the runtime dependency floor for `snaky_hash` to `>= 2.0.5`.
+
+### Security
+
+- Hardened OAuth token endpoint redirect handling after the GHSA-pp92-crg2-gfv9
+  review: token redirects are now bounded, resolved explicitly, and rejected
+  when they cross origins unless explicitly enabled.
+
 ## [1.1.5] - 2026-05-20
 
 - TAG: [v1.1.5][1.1.5t]
@@ -764,7 +786,9 @@ All together now release
 - Moved all non-Rails functionality from the Rails plugin:
   http://code.google.com/p/oauth-plugin/
 
-[Unreleased]: https://github.com/ruby-oauth/oauth/compare/v1.1.5...HEAD
+[Unreleased]: https://github.com/ruby-oauth/oauth/compare/v1.1.6...HEAD
+[1.1.6]: https://github.com/ruby-oauth/oauth/compare/v1.1.5...v1.1.6
+[1.1.6t]: https://github.com/ruby-oauth/oauth/releases/tag/v1.1.6
 [1.1.5]: https://github.com/ruby-oauth/oauth/compare/v1.1.4...v1.1.5
 [1.1.5t]: https://github.com/ruby-oauth/oauth/releases/tag/v1.1.5
 [1.1.4]: https://github.com/ruby-oauth/oauth/compare/v1.1.3...v1.1.4

data/CITATION.cff

@@ -1,19 +1,19 @@
 cff-version: 1.2.0
-title: oauth
+title: "oauth"
 message: >-
   If you use this work and you want to cite it,
   then you can use the metadata from this file.
 type: software
 authors:
-  - given-names: Peter Hurn
-    family-names: Boling
-    email: peter@railsbling.com
-    affiliation: railsbling.com
+  - given-names: "Peter H."
+    family-names: "Boling"
+    email: "floss@galtzo.com"
+    affiliation: "galtzo.com"
     orcid: 'https://orcid.org/0009-0008-8519-441X'
 identifiers:
   - type: url
     value: 'https://github.com/ruby-oauth/oauth'
-    description: oauth
+    description: "oauth"
 repository-code: 'https://github.com/ruby-oauth/oauth'
 abstract: >-
   oauth

data/CONTRIBUTING.md

@@ -8,29 +8,37 @@ To submit a patch, please fork the project, create a patch with tests, and send
 
 Remember to [![Keep A Changelog][📗keep-changelog-img]][📗keep-changelog] if you make changes.
 
+## Developer Certificate of Origin
+
+In order to protect users of this project, we require all contributors to comply with the
+[Developer Certificate of Origin](https://developercertificate.org/).
+This ensures that all contributions are properly licensed and attributed.
+
 ## Help out!
 
-Take a look at the `reek` list which is the file called `REEK` and find something to improve.
+Take a look at the open issues and pull requests, or use the gem and find something to improve.
 
 Follow these instructions:
 
-1. Fork the repository
-2. Create a feature branch (`git checkout -b my-new-feature`)
-3. Make some fixes.
-4. Commit changes (`git commit -am 'Added some feature'`)
-5. Push to the branch (`git push origin my-new-feature`)
-6. Make sure to add tests for it. This is important, so it doesn't break in a future release.
-7. Create new Pull Request.
+1. Join the Discord: [![Live Chat on Discord][✉️discord-invite-img]][✉️discord-invite]
+2. Fork the repository
+3. Create your feature branch (`git checkout -b my-new-feature`)
+4. Make some fixes.
+5. Commit your changes (`git commit -am 'Added some feature'`)
+6. Push to the branch (`git push origin my-new-feature`)
+7. Make sure to add tests for it. This is important, so it doesn't break in a future release.
+8. Create new Pull Request.
+9. Announce it in the channel for this org in the [Discord][✉️discord-invite]!
 
 ## Executables vs Rake tasks
 
-Executables shipped by dependencies, such as oauth, and stone_checksums, are available
+Executables shipped by dependencies, such as kettle-dev, and stone_checksums, are available
 after running `bin/setup`. These include:
 
 - gem_checksums
 - kettle-changelog
 - kettle-commit-msg
-- oauth-setup
+- kettle-dev-setup
 - kettle-dvcs
 - kettle-pre-release
 - kettle-readme-backers
@@ -42,6 +50,22 @@ There are many Rake tasks available as well. You can see them by running:
 bin/rake -T
 ```
 
+## Code quality checks
+
+Run the Reek task when you want a smell check that fails on current findings:
+
+```shell
+bin/rake reek
+```
+
+Refresh the checked-in `REEK` backlog through the rake task, not by redirecting
+the raw `reek` executable output. The rake task uses the project bundle and
+avoids stale generated binstubs shadowing the Reek gem executable:
+
+```shell
+bin/rake reek:update
+```
+
 ## Environment Variables for Local Development
 
 Below are the primary environment variables recognized by stone_checksums (and its integrated tools). Unless otherwise noted, set boolean values to the string "true" to enable.
@@ -52,7 +76,7 @@ General/runtime
 - CI: When set to true, adjusts default rake tasks toward CI behavior
 
 Coverage (kettle-soup-cover / SimpleCov)
-- K_SOUP_COV_DO: Enable coverage collection (default: true in .envrc)
+- K_SOUP_COV_DO: Enable coverage collection (default: true in `mise.toml`)
 - K_SOUP_COV_FORMATTERS: Comma-separated list of formatters (html, xml, rcov, lcov, json, tty)
 - K_SOUP_COV_MIN_LINE: Minimum line coverage threshold (integer, e.g., 100)
 - K_SOUP_COV_MIN_BRANCH: Minimum branch coverage threshold (integer, e.g., 100)
@@ -68,7 +92,9 @@ GitHub API and CI helpers
 Releasing and signing
 - SKIP_GEM_SIGNING: If set, skip gem signing during build/release
 - GEM_CERT_USER: Username for selecting your public cert in `certs/<USER>.pem` (defaults to $USER)
-- SOURCE_DATE_EPOCH: Reproducible build timestamp. `kettle-release` will set this automatically for the session.
+- SOURCE_DATE_EPOCH: Reproducible build timestamp.
+  - `kettle-release` will set this automatically for the session.
+  - Not needed on bundler >= 2.7.0, as reproducible builds have become the default.
 
 Git hooks and commit message helpers (exe/kettle-commit-msg)
 - GIT_HOOK_BRANCH_VALIDATE: Branch name validation mode (e.g., `jira`) or `false` to disable
@@ -76,35 +102,60 @@ Git hooks and commit message helpers (exe/kettle-commit-msg)
 - GIT_HOOK_FOOTER_SENTINEL: Required when footer append is enabled — a unique first-line sentinel to prevent duplicates
 - GIT_HOOK_FOOTER_APPEND_DEBUG: Extra debug output in the footer template (true/false)
 
-For a quick starting point, this repository’s `.envrc` shows sane defaults, and `.env.local` can override them locally.
+Git diff driver setup
+- Local setup writes repository `.gitattributes` entries and local Git `diff.smorg-*` command config so this checkout uses StructuredMerge semantic diffs.
+- Global setup registers `diff.smorg-*` commands once in the user Git config; use it when you work across several StructuredMerge-enabled repositories.
+- Include-file setup writes `.git/smorg/config` and includes it from local Git config, keeping command registrations out of the repository files.
+- Git hosting forges generally ignore external diff drivers, so pull request views may still show raw textual diffs even when local `git diff` uses semantic drivers.
+
+```console
+K_JEM_TEMPLATING=true bundle exec kettle-jem install
+```
+
+Troubleshooting Git diffs
+- Use `git diff --no-ext-diff` to compare against Git's built-in diff output.
+- Use `git diff --no-textconv` when a textconv projection obscures the raw file bytes you need to inspect.
+- If Git reports a missing `smorg-*` executable, rerun `bundle install` and the setup command above, then check `git config --local --get-regexp '^diff\.smorg-'`.
+- To remove managed local entries, run `K_JEM_TEMPLATING=true bundle exec kettle-jem install --undo`; remove global command registrations with `git config --global --unset-all diff.smorg-ruby.command`.
+
+For a quick starting point, this repository’s `mise.toml` defines the shared defaults, and `.env.local` can override them locally. Copy `.env.local.example` to `.env.local`, use `KEY=value` lines, and either activate `mise` in your shell or run commands through `mise exec -C /path/to/project -- ...`.
 
 ## Appraisals
 
 From time to time the [appraisal2][🚎appraisal2] gemfiles in `gemfiles/` will need to be updated.
+Generated appraisal and CI workflow floors are controlled by `ruby.test_minimum`
+in `.structuredmerge/kettle-jem.yml`; this project was templated with `ruby.test_minimum: 2.4`.
+That value describes the lowest Ruby version expected to run the test/development
+toolchain, and it may be higher than the gemspec runtime floor.
+
 They are created and updated with the commands:
 
 ```console
 bin/rake appraisal:update
 ```
 
-When adding an appraisal to CI, check the [runner tool cache][🏃‍♂️runner-tool-cache] to see which runner to use.
+If you need to reset all gemfiles/*.gemfile.lock files:
+
+```console
+bin/rake appraisal:reset
+```
 
-## The Reek List
+When adding an appraisal to CI, check the [runner tool cache][🏃‍♂️runner-tool-cache] to see which runner to use.
 
-Take a look at the `reek` list which is the file called `REEK` and find something to improve.
+## Run Tests
 
-To refresh the `reek` list:
+Run tests via `kettle-test` (provided by `kettle-test`). It runs RSpec, writes the full log to
+`tmp/kettle-test/rspec-TIMESTAMP.log`, and prints a compact highlight block with timing, seed,
+pass/fail count, failing example list, and SimpleCov coverage percentages.
 
 ```console
-bundle exec reek > REEK
+bundle exec kettle-test
 ```
 
-## Run Tests
-
-To run all tests
+For targeted runs, disable the hard coverage threshold to avoid false failures:
 
 ```console
-bundle exec rake test
+K_SOUP_COV_MIN_HARD=false bundle exec kettle-test spec/path/to/spec.rb
 ```
 
 ### Spec organization (required)
@@ -168,39 +219,41 @@ NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in th
 1. Update version.rb to contain the correct version-to-be-released.
 2. Run `bundle exec kettle-changelog`.
 3. Run `bundle exec kettle-release`.
+4. Stay awake and monitor the release process for any errors, and answer any prompts.
 
 #### Manual process
 
 1. Run `bin/setup && bin/rake` as a "test, coverage, & linting" sanity check
 2. Update the version number in `version.rb`, and ensure `CHANGELOG.md` reflects changes
 3. Run `bin/setup && bin/rake` again as a secondary check, and to update `Gemfile.lock`
-4. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
-5. Run `git push` to trigger the final CI pipeline before release, and merge PRs
+4. Run `bin/rake yard` to regenerate the docs site using the canonical docs task
+5. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
+6. Run `git push` to trigger the final CI pipeline before release, and merge PRs
     - NOTE: Remember to [check the build][🧪build].
-6. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
-7. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
-8. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure latest trunk code
-9. Optional for older Bundler (< 2.7.0): Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use the same timestamp and generate the same checksums
+7. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
+8. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
+9. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure latest trunk code
+10. Optional for older Bundler (< 2.7.0): Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use the same timestamp and generate the same checksums
     - If your Bundler is >= 2.7.0, you can skip this; builds are reproducible by default.
     - Run `export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH`
     - If the echo above has no output, then it didn't work.
     - Note: `zsh/datetime` module is needed, if running `zsh`.
     - In older versions of `bash` you can use `date +%s` instead, i.e. `export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH`
-10. Run `bundle exec rake build`
-11. Run `bin/gem_checksums` (more context [1][🔒️rubygems-checksums-pr], [2][🔒️rubygems-guides-pr])
+11. Run `bundle exec rake build`
+12. Run `bin/gem_checksums` (more context [1][🔒️rubygems-checksums-pr], [2][🔒️rubygems-guides-pr])
     to create SHA-256 and SHA-512 checksums. This functionality is provided by the `stone_checksums`
     [gem][💎stone_checksums].
     - The script automatically commits but does not push the checksums
-12. Sanity check the SHA256, comparing with the output from the `bin/gem_checksums` command:
+13. Sanity check the SHA256, comparing with the output from the `bin/gem_checksums` command:
     - `sha256sum pkg/<gem name>-<version>.gem`
-13. Run `bundle exec rake release` which will create a git tag for the version,
+14. Run `bundle exec rake release` which will create a git tag for the version,
     push git commits and tags, and push the `.gem` file to the gem host configured in the gemspec.
 
-[📜src-gl]: https://gitlab.com/ruby-oauth/oauth/
+[📜src-gl]: https://gitlab.com/ruby-oauth/oauth
 [📜src-cb]: https://codeberg.org/ruby-oauth/oauth
 [📜src-gh]: https://github.com/ruby-oauth/oauth
 [🧪build]: https://github.com/ruby-oauth/oauth/actions
-[🤝conduct]: https://gitlab.com/ruby-oauth/oauth/-/blob/main/CODE_OF_CONDUCT.md
+[🤝conduct]: https://github.com/ruby-oauth/oauth/blob/main/CODE_OF_CONDUCT.md
 [🖐contrib-rocks]: https://contrib.rocks
 [🖐contributors]: https://github.com/ruby-oauth/oauth/graphs/contributors
 [🚎contributors-gl]: https://gitlab.com/ruby-oauth/oauth/-/graphs/main
@@ -216,3 +269,4 @@ NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in th
 [📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
 [🚎appraisal2]: https://github.com/appraisal-rb/appraisal2
 [🏃‍♂️runner-tool-cache]: https://github.com/ruby/ruby-builder/releases/tag/toolcache
+[✉️discord-invite]: https://discord.gg/3qme4XHNKN

data/FUNDING.md

@@ -19,7 +19,7 @@ Many paths lead to being a sponsor or a backer of this project. Are you on such
 [🖇polar-img]: https://img.shields.io/badge/polar-donate-a51611.svg?style=flat
 [🖇polar]: https://polar.sh/pboling
 [🖇kofi-img]: https://img.shields.io/badge/ko--fi-%E2%9C%93-a51611.svg?style=flat
-[🖇kofi]: https://ko-fi.com/O5O86SNP4
+[🖇kofi]: https://ko-fi.com/pboling
 [🖇patreon-img]: https://img.shields.io/badge/patreon-donate-a51611.svg?style=flat
 [🖇patreon]: https://patreon.com/galtzo
 [🖇buyme-small-img]: https://img.shields.io/badge/buy_me_a_coffee-%E2%9C%93-a51611.svg?style=flat
@@ -31,11 +31,11 @@ Many paths lead to being a sponsor or a backer of this project. Are you on such
 
 <!-- RELEASE-NOTES-FOOTER-END -->
 
-# 🤑 Request for Help
+# 🤑 A request for help
 
 Maintainers have teeth and need to pay their dentists.
-After getting laid off in an RIF in March and filled with many dozens of rejections,
-I'm now spending ~60+ hours a week building open source tools.
+After getting laid off in an RIF in March, and encountering difficulty finding a new one,
+I began spending most of my time building open source tools.
 I'm hoping to be able to pay for my kids' health insurance this month,
 so if you value the work I am doing, I need your support.
 Please consider sponsoring me or the project.
@@ -44,16 +44,13 @@ To join the community or get help 👇️ Join the Discord.
 
 [![Live Chat on Discord][✉️discord-invite-img-ftb]][✉️discord-invite]
 
-To say "thanks for maintaining such a great tool" ☝️ Join the Discord or 👇️ send money.
+To say "thanks!" ☝️ Join the Discord or 👇️ send money.
 
 [![Sponsor ruby-oauth/oauth on Open Source Collective][🖇osc-all-bottom-img]][🖇osc] 💌 [![Sponsor me on GitHub Sponsors][🖇sponsor-bottom-img]][🖇sponsor] 💌 [![Sponsor me on Liberapay][⛳liberapay-bottom-img]][⛳liberapay] 💌 [![Donate on PayPal][🖇paypal-bottom-img]][🖇paypal]
 
 # Another Way to Support Open Source Software
 
-> How wonderful it is that nobody need wait a single moment before starting to improve the world.<br/>
->—Anne Frank
-
-I’m driven by a passion to foster a thriving open-source community – a space where people can tackle complex problems, no matter how small.  Revitalizing libraries that have fallen into disrepair, and building new libraries focused on solving real-world challenges, are my passions — totaling 79 hours of FLOSS coding over just the past seven days, a pretty regular week for me.  I was recently affected by layoffs, and the tech jobs market is unwelcoming. I’m reaching out here because your support would significantly aid my efforts to provide for my family, and my farm (11 🐔 chickens, 2 🐶 dogs, 3 🐰 rabbits, 8 🐈‍ cats).
+I’m driven by a passion to foster a thriving open-source community – a space where people can tackle complex problems, no matter how small.  Revitalizing libraries that have fallen into disrepair, and building new libraries focused on solving real-world challenges, are my passions.  I was recently affected by layoffs, and the tech jobs market is unwelcoming. I’m reaching out here because your support would significantly aid my efforts to provide for my family, and my farm (11 🐔 chickens, 2 🐶 dogs, 3 🐰 rabbits, 8 🐈‍ cats).
 
 If you work at a company that uses my work, please encourage them to support me as a corporate sponsor. My work on gems you use might show up in `bundle fund`.
 

data/LICENSE.md

@@ -0,0 +1,71 @@
+# License
+
+This project is made available under the following license.
+Choose the option that best fits your use case:
+
+- [MIT](MIT.md)
+
+## Copyright Notice
+
+- Copyright (c) 2007-2010 Pelle Braendgaard
+- Copyright (c) 2008 Chris Mear
+- Copyright (c) 2008 Jon Crosby
+- Copyright (c) 2008-2010 Seth Fitzsimmons
+- Copyright (c) 2008 Tilmann Singer
+- Copyright (c) 2008 Tom Insam
+- Copyright (c) 2008 tsailipu
+- Copyright (c) 2009-2012 Aaron Quint
+- Copyright (c) 2009 Anders Conbere
+- Copyright (c) 2009 Bill Kocik
+- Copyright (c) 2009 Darcy Laycock
+- Copyright (c) 2009 Eric Hartmann
+- Copyright (c) 2009 Greg Weber
+- Copyright (c) 2009 Laszlo Bacsi
+- Copyright (c) 2009 Marshall Huss
+- Copyright (c) 2009 Matt Sanford
+- Copyright (c) 2009 Neill Pearman
+- Copyright (c) 2009 Seth Cousins
+- Copyright (c) 2009 Yoan Blanc
+- Copyright (c) 2010 andrehjr
+- Copyright (c) 2010 Brian Finney
+- Copyright (c) 2010 ecavazos
+- Copyright (c) 2010 Joshua Hull
+- Copyright (c) 2010 Marsh Gardiner
+- Copyright (c) 2010 Michael Reinsch
+- Copyright (c) 2010 Sean Cribbs
+- Copyright (c) 2010 Steven Parkes
+- Copyright (c) 2010 成田 一生
+- Copyright (c) 2011 Shaliko Usubov
+- Copyright (c) 2012 Ernie Miller
+- Copyright (c) 2012 Jonathon M. Abbott
+- Copyright (c) 2012 Richard Huang
+- Copyright (c) 2012 rick
+- Copyright (c) 2012 Steven Hammond
+- Copyright (c) 2013 Craig Walker
+- Copyright (c) 2013 Khem Veasna
+- Copyright (c) 2014 Brian John
+- Copyright (c) 2014 Michal Papis
+- Copyright (c) 2014 raeno
+- Copyright (c) 2015 jremmen
+- Copyright (c) 2015 Kevin Hughes
+- Copyright (c) 2016 Eric True
+- Copyright (c) 2016-2017 James Pinto
+- Copyright (c) 2016 jianben
+- Copyright (c) 2016 Nik Wakelin
+- Copyright (c) 2017 Ondrej Prazak
+- Copyright (c) 2018 Nicholas Souphandavong
+- Copyright (c) 2018 Yvonne
+- Copyright (c) 2019 Agora@Ubuntu-dev
+- Copyright (c) 2019 Shohei Maeda
+- Copyright (c) 2020-2021, 2026 Khem
+- Copyright (c) 2021 Chuck Remes
+- Copyright (c) 2021 iamibi
+- Copyright (c) 2021 Jeremy Sioui
+- Copyright (c) 2021 Nick Morgan
+- Copyright (c) 2021-2022, 2025-2026 Peter H. Boling
+- Copyright (c) 2021 Richard Vowles
+- Copyright (c) 2022 Shalvah
+- Copyright (c) 2024-2025 Annibelle Boling
+- Copyright (c) 2025 Aboling0
+- Copyright (c) 2026 David Varga
+- Copyright (c) 2026 StepSecurity Bot