Skip to content

docs(security): policy names a release number and outdated storage #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kaulith merged 1 commit into from
Oct 15, 2026
Merged

docs(security): policy names a release number and outdated storage #102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@ next tagged release; older tags do not get patches.

| Version | Supported |
| ------- | --------- |
| 1.1.0 (latest release) | Yes |
| Older tags | No |
| Latest release | Yes |
| Older releases | No |

## Reporting a vulnerability

Expand Down Expand Up @@ -44,7 +44,8 @@ anonymous. This is an unpaid project; there is no bug bounty.
In scope, in this repository:

- storage and handling of site credentials and OAuth tokens; the app keeps API keys,
secrets and tokens in `EncryptedSharedPreferences` under an AES256-GCM master key
secrets and tokens encrypted with an AES256-GCM key held in the Android Keystore,
in a separate store for each site you add
- the API client and anything that could send credentials or ticket data somewhere other
than the configured site
- the local Room cache of tickets and agents, and what an attacker with device access
Expand All @@ -67,6 +68,8 @@ Out of scope:

## Notes for reporters

The app talks only to the site URL you configure, and it is distributed as a signed APK
from the GitHub releases page of this repository. An APK from anywhere else is not ours
The app talks to the helpdesk sites you add and to GitHub, to check for a newer release.
For support.frappe.io, which cannot run the push app, the phone registers for alerts on
the project's push server and sends that site's token there to prove who it is. The app
is distributed as a signed APK from the GitHub releases page of this repository. An APK from anywhere else is not ours
and is not covered by this policy.
Loading