Merge 36f5b04220 into d6abd6d3e5

.github/workflows/Build.yaml

@@ -190,8 +190,12 @@ jobs:
       - name: Check badging
         run: ./gradlew :app:checkProdReleaseBadging
 
-  androidTest:
-    runs-on: ubuntu-latest
+androidTest:
+runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write
+      
     timeout-minutes: 55
     strategy:
       matrix:

.github/workflows/Release.yml

@@ -1,5 +1,9 @@
 name: GitHub Release with APKs
 
+permissions:
+  contents: write
+
+
 on:
   workflow_dispatch:
   push:

LICENSE

@@ -187,7 +187,8 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright [yyyy] [name of copyright owner]
+   Copyright PichaiTK​ name of copyright owner
+   
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

LICENSE-Markdown.md

@@ -0,0 +1,33 @@
+````markdown name=LICENSES.md
+# Licenses included in this repository
+
+This repository includes multiple license texts to make it simple to pick and apply the license that suits your project and its components.
+
+Files provided:
+- `LICENSE` — MIT License (recommended default). Short, permissive, widely used.
+- `LICENSE.APACHE-2.0` — Apache License 2.0 (if you want patent grant and a few additional protections).
+- `LICENSES.md` — this file (you are reading it).
+
+If you want to apply a single license to the entire repository, pick one of the files above and keep it as `LICENSE` at the repository root. The current default `LICENSE` file contains the MIT license and is assigned to the project by default.
+
+Recommended actions:
+1. Choose one license (MIT or Apache-2.0) for the project. Remove extra license files if you do not plan to multi-license.
+2. Add a short SPDX header to each source file (see `SPDX-HEADERS.txt` for examples).
+3. If you accept contributions and want them under the project's license, include a CONTRIBUTING.md that states the contributor license expectations (Contributor License Agreement or DCO).
+4. If you plan to dual-license, make that explicit in the repository README and each release.
+
+Notes about licenses:
+- MIT is permissive: allows reuse with minimal obligations (must keep copyright & license).
+- Apache-2.0 is permissive and includes an explicit patent grant and patent retaliation clause.
+- GPL-3.0 (not included as a text file here) is copyleft (derivative works must be licensed under GPL-3.0). If you need GPL, add `COPYING` with the GPL-3.0 text.
+
+SPDX expressions:
+- To mark the project as MIT: `SPDX-License-Identifier: MIT`
+- For Apache 2.0: `SPDX-License-Identifier: Apache-2.0`
+
+If you want, I can:
+- Replace the repository `LICENSE` with Apache-2.0 or GPL-3.0 in full.
+- Add SPDX headers automatically to all TS/JS/PY files in the repo.
+- Add a `CONTRIBUTING.md` describing contributor license terms (DCO / CLA).
+
+

License-mit.md

@@ -0,0 +1,23 @@
+MIT License
+
+Copyright (c) 2026 Pichai​ ​Takengrach​
+
+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.
+
+

SECURITY.md

@@ -0,0 +1,22 @@
+# Security Policy
+
+## Supported Versions
+
+Use this section to tell people about which versions of your project are
+currently being supported with security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 5.1.x   | :white_check_mark: |
+| 5.0.x   | :x:                |
+| 4.0.x   | :white_check_mark: |
+| < 4.0   | :x:                |
+
+## Reporting a Vulnerability
+
+Use this section to tell people how to report a vulnerability.
+
+Tell them where to go, how often they can expect to get an update on a
+reported vulnerability, what to expect if the vulnerability is accepted or
+declined, etc.
+