From a0df796d2b6afece391b40f5b3ac70e218bfe600 Mon Sep 17 00:00:00 2001 From: nay1719 Date: Mon, 1 Jun 2026 13:49:37 +0100 Subject: [PATCH 1/3] Revise SECURITY.md for clarity on support and reporting Updated the security policy to clarify supported versions and vulnerability reporting. --- SECURITY.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..90c4a62 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,15 @@ + +We maintain updates and patches in the latest release. Earlier versions will still work, but will have less functionalities than later versions. +We encourage all users of these service layers to update to the latest version for the best experience. + +| Version | Supported | +| ------- | ------------------ | +| 3.5.x | :white_check_mark: | +| < 3.4 | :x: | + +## Reporting a Vulnerability + +Thank you for letting us know about possible security vulnerabilities to this project. +Please don’t publish details in a public issue or PR, send us a private email at support@approov.io. Please disclose which version your report refers to. + +Your message will recieve a prompt reply. From 8eca2856fd77d935cc55e985341ead2e02194782 Mon Sep 17 00:00:00 2001 From: nay1719 Date: Mon, 1 Jun 2026 14:07:53 +0100 Subject: [PATCH 2/3] Add MIT License to the project --- LICENSE | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 LICENSE diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..eabfcad --- /dev/null +++ b/LICENSE @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2026 Approov Integration Examples + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. From bef6b045d60e11fb6dd29235d8b701c566f61ea4 Mon Sep 17 00:00:00 2001 From: ivol Date: Tue, 9 Jun 2026 15:46:52 +0100 Subject: [PATCH 3/3] fix: correct spelling in SECURITY.md and copyright holder in LICENSE --- LICENSE | 2 +- SECURITY.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/LICENSE b/LICENSE index eabfcad..5b349ed 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2026 Approov Integration Examples +Copyright (c) 2026 Critical Blue Ltd. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/SECURITY.md b/SECURITY.md index 90c4a62..6bce9bc 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -12,4 +12,4 @@ We encourage all users of these service layers to update to the latest version f Thank you for letting us know about possible security vulnerabilities to this project. Please don’t publish details in a public issue or PR, send us a private email at support@approov.io. Please disclose which version your report refers to. -Your message will recieve a prompt reply. +Your message will receive a prompt reply.