woaiys3 / deepseek-harness-android-app
DeepSeek Harness 手机版:可直接安装的 Android APK,AI 免 Root 操作手机(Shizuku/root 可选),文件编辑只需所有文件访问权限,前台保活 + AI 通知
DeepSeek Harness mobile version: a directly installable Android APK that lets AI operate the phone without Root (Shizuku/root optional), file editing only requires all-files access permission, foreground keep-alive + AI notifications Machine translation by Claude Sonnet 5.5. A wrong translation? Report an error
- Stars
- 699 stars
- Forks
- 47 forks
- Language
- Java
- License
- MIT
- Created
- Aug 16, 2026
- Last push
- Oct 18, 2026
- Updated
- Nov 20, 2026
Why these Tags: an agent read the README and quoted it
- Android app from the readme:
把 DeepSeek Harness(DSH)打包成**可直接安装的 Android APK**
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Oct 23, 2026: +113 stars in 7 days.
Star History
75 days recorded, Aug 16, 2026 – Nov 20, 2026 (UTC). 22 days in this period have no record and show as gaps. Net change +705 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/woaiys3/deepseek-harness-android-app) Badge
[](https://awesomerepos.com/woaiys3/deepseek-harness-android-app) Timeline
It gained stars on each of the 75 days recorded since Aug 16, 2026.
Its largest 7 days were Oct 20, 2026 to Oct 26, 2026: 126 stars.
- Created on the Repository Host
- Reached 100 stars, 9 days after it was created
- Reached 500 stars, 63 days after it was created
- Largest star day recorded: +21 stars
- Latest push
- +21 stars in one day
- Entered the Repository Index: +113 stars in 7 days
- +21 stars in one day
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 7 Observations, Oct 24, 2026 – Nov 21, 2026. Forks +7. AwesomeRepos saw a new push on 0 of 6 days.
- Oct 25, 2026: no new push
- Oct 26, 2026: no new push
- Oct 27, 2026: no new push
- Oct 28, 2026: no new push
- Oct 29, 2026: no new push
- Nov 21, 2026: no new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos last read these facts from GitHub on Nov 21, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of woaiys3/deepseek-harness-android-app.
Improve the Health Facts of the GitHub repository woaiys3/deepseek-harness-android-app. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/woaiys3/deepseek-harness-android-app. A change to the repository can improve each of the 2 items below. Each item gives the measured fact or score, and a task. 1. A release in the last 365 days Fact: No GitHub release (read on 2026-11-09). Rule: The newest published GitHub release (a pre-release counts; a draft does not) is 365 days old or less. A repository that publishes only tags, or only to a package registry, has no GitHub release. The release refresh reads the 10 newest releases after each push to the repository, and at least each 30 days. The index refresh reads the date of the last push each day. Task: Prepare a release, but do not publish it. Find the changes since the newest release, propose the next semantic version and the release notes, and ask me to publish the GitHub release. If nothing changed since the newest release, skip this item. If the project publishes only to a package registry, add a CI step that also makes a GitHub release for each version tag. 2. A security policy Fact: GitHub finds no security policy (GitHub, 2026-11-21). Rule: GitHub finds a security policy (SECURITY.md in the repository or in the owner's .github repository). Task: Add SECURITY.md at the root or in .github/. Say which versions get security fixes and how to report a vulnerability privately. If GitHub private vulnerability reporting is on, point to it. Ask me for the contact; do not invent one. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
3 of 4 checks-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-10-18, 34 days ago. Source
-
Yes: Commits in the last 13 weeks
266 commits on the default branch in the last 13 weeks (GitHub, 2026-11-21). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 7 of the last 52 weeks (GitHub, 2026-11-21). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 32
- 127
- 0
- 0
- 60
- 37
- 33
- 5
- 0
- 4
- 0
- 0
- 0
- 0
Releases
1 of 3 checks (1 without data)Security practice
0 of 1 check-
No: A security policy
GitHub finds no security policy (GitHub, 2026-11-21).
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
3 of 3 checksDependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
GitHub has no dependency graph for this repository (scanned on Nov 21, 2026).
No scanned repository names a package from this repository.
Uses (in the index) · 0
None.
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package . A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 21, 2026: 699 stars, 47 forks, last push Oct 18, 2026, not archived. One of 29 Observations since Oct 24, 2026.