Skip to content
Projects

capitan0n/droynis has 40 GitHub stars and 4 forks. GitHot measured +4 stars in 24 hours. Last checked 2026-11-15 21:46 UTC. Last push 2026-11-11.

How these counts are measured

40 stars4 Forks +4 in 24h

Measured star growth

in 24h
+4
in 7 days
Collecting history
in 15 days
Collecting history
in 1 month
Collecting history

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Offline Android security audit tool. 90 read-only checks across multiple privilege levels (base, ADB, Shizuku, root), 0–100 score and saved reports. Privacy-oriented, no internet permission, zero telemetry, fully local.

Security

README.md

Original

Droynis

A read-only security and privacy audit for Android, inspired by Lynis (Android+Lynis). Droynis checks the phone it runs on, explains every finding, shows the evidence and opens the Settings screen that fixes it. It never changes anything itself.

Not an antivirus or malware scanner. Droynis doesn't scan apps or files for malicious code and doesn't remove anything. It audits how the phone is set up: what is locked, patched, exposed and granted. It can point out risky access, such as an app with accessibility or device-admin rights, and signs that adware leaves, such as an app that hides from the app drawer and runs on its own, but it can't tell you whether that app is malware.

  • 90 checks: device integrity, access control, apps and permissions, suspicious apps, network and radios. Every check, with when it fails and what to do: docs/CHECKS.md.
  • No INTERNET permission, no Google Play Services, no analytics. Nothing leaves the phone unless you share a report.
  • A check passes only on a value it actually read. When Android won't say, the result is Unknown, never Passed.

Droynis is an independent project, not affiliated with, endorsed by or connected to Lynis or CISOfy, and shares no code with it.

Install

Android 8.0 or later. Pick one:

1. F-Droid

Get it on F-Droid

Install from the F-Droid page or search for Droynis in the F-Droid client, which also keeps it updated. F-Droid builds each version from the tagged source, so it may appear a few days after the GitHub release.

2. GitHub Releases

Download the APK from Releases and verify it before installing:

sha256sum -c droynis-<version>.apk.sha256
gh attestation verify droynis-<version>.apk --repo capitan0n/droynis   # built by GitHub from the tag

Each release lists the signing certificate's SHA-256.

3. Obtainium

Get it on Obtainium

Obtainium installs each GitHub release directly, with no store delay: tap the badge on your phone, or in Obtainium tap Add App and enter https://github.com/capitan0n/droynis. Pre-releases are skipped unless you turn on Include prereleases.

On first install, check that the signing certificate matches the SHA-256 in the release notes (for example with AppVerifier); Android then refuses any update signed with another key.

Tiers

Tier Setup Adds
Base none 53 checks through public Android APIs
ADB two grants from a computer, once 13 checks from dumpsys: special app access, screen capture without asking, Smart Lock, background camera, microphone and location use, Wi-Fi MAC randomization, open Wi-Fi networks that join automatically, hidden Wi-Fi networks, hotspot security
Shizuku the Shizuku app SELinux, spoofed boot properties, always-on VPN lockdown, SIM PIN, device controls on the lock screen, passkey and password providers, clipboard access alerts, mobile network encryption and fake cell tower alerts; reads what Android hides from apps, and runs the ADB checks
Root opt-in switch in the app trusted computers, apps with root, root modules, root boot scripts others can change, programs staged in shared temp, root access over ADB, apps listening on the network; runs the ADB and Shizuku checks

In the app, ⋮ › Check catalog shows which tiers are active and how to set up the rest. Shizuku and root run only a fixed set of read-only commands; root stays off until you turn it on.

Setting up the ADB tier

Android hides dumpsys output from apps unless they hold DUMP and PACKAGE_USAGE_STATS, and only a computer with adb can grant those two. You don't need this if you use Shizuku or root.

  1. On the phone, turn on Developer options › USB debugging and connect it to a computer with adb (Arch/Manjaro: android-tools, Debian/Ubuntu: adb).

  2. Grant the two permissions:

    adb shell pm grant io.github.capitan0n.droynis android.permission.DUMP
    adb shell pm grant io.github.capitan0n.droynis android.permission.PACKAGE_USAGE_STATS
    
  3. Tap Scan again, then turn USB debugging off; Droynis reports it as a risk when it's on.

The grants survive reboots and stay until you uninstall the app or run the same commands with pm revoke. They let Droynis read, never change, system state.

Score and reports

The score is passed weight ÷ scored weight × 100 (critical 10, warning 5, notice 2, info 0); a critical failure caps it at 40. Unknown, N/A and muted checks don't count. Mute what you can't fix, such as a patch level only the maker can update; the Muted filter has Unmute all.

Some apps need a lot of access to do their job, such as a watch app that reads notifications and SMS. Instead of muting whole checks, open one that lists the app and tap Trust under it: the app stays listed in every check but no longer counts in any of them. ⋮ › Trusted apps shows where each one is listed and removes them, and reports name every trusted app.

⋮ › Save the report as Markdown or JSON, or share it; Reports › Report can also copy it. Hide personal details (on by default) replaces IP addresses, DNS and proxy servers, the Private DNS host, trusted computers and saved Wi-Fi network names with [hidden]. JSON reports keep a fixed order, so you can compare two scans with diff.

Scheduled scans

Reports › Scheduled scan (off by default) scans about once a day or once a week in the background, through Android's JobScheduler. With Notifications on, every scheduled scan ends with a notification: Verbose notification (on by default) lists which checks got worse, got fixed or couldn't run; off, it gives only the score and the previous one. With notifications off, scans run quietly and the card shows the last result. A scheduled scan uses the tiers available at that moment: checks that can't run then (say, Shizuku stopped after a reboot) keep their last result and are not reported as changes. On the lock screen the notification only says that a scan finished.

This adds two permissions: POST_NOTIFICATIONS (Android 13+ asks only when you turn notifications on) and RECEIVE_BOOT_COMPLETED, which JobScheduler needs to keep the schedule across reboots. While a schedule is on, Droynis keeps the last result of each check (its id and status, nothing else) in its private storage to compare against; turning the schedule off deletes it. Android may delay background work to save battery, so daily means about daily.

When Android holds the scans back, the card says so and opens App info: with Droynis' battery usage set to Restricted (background usage not allowed), scans wait until you open the app; and a scan that starts more than 6 hours past the window Android gives itself is reported as late, which battery savers that put apps to sleep (Samsung, Xiaomi, OnePlus) often cause. Choosing Unrestricted fixes that, but Droynis' own check APPS-4013 then lists it: trust Droynis to leave it out.

Build

JDK 21 and the Android SDK (compileSdk 37).

./gradlew check          # unit tests, lint, and docs/CHECKS.md matching the code
./gradlew assembleDebug  # app/build/outputs/apk/debug/app-debug.apk

assembleRelease signs with keystore.properties (git-ignored) or DROYNIS_* environment variables, and builds an unsigned APK without them, as F-Droid expects. Debug builds are slow by design; use a release build day to day. Releases: docs/RELEASING.md.

More

Author: Alexandros (capitan0n) · https://github.com/capitan0n · [email protected]

License: GNU General Public License v3.0 or later (GPL-3.0-or-later), see LICENSE.