githubXiaowangzi / NP-Manager
Apk控制流混淆；Apk-Dex2C；Res资源混淆；Dex、jar、smali文件的相互转换； Dex、Pdf文件合并； Apk、dex、jar混淆和字符串加密； Apk签名、共存； Res资源混淆； Dex、AXML、ARSC文件编辑及翻译；字符串加密(Apk、dex)； 一键添加Xposed检测，一键添加弹窗、对话框； axml反编译/回编译； 一键LOG添加； 一键添加字符串解密LOG，Dex文件换包名； 一键添加禁止截屏，一键添加Apk崩溃日志记录； Apk超级混淆3.0--高效率直接对dex混淆，支持混淆四大组件，支持多dex； Apk功能--DEX混淆对抗；屏幕取色器；屏幕标尺。
- Stars
- 1,885 stars
- Forks
- 125 forks
- Language
- PHP
- License
- Not reported
- Created
- Dec 8, 2019
- Last push
- Nov 9, 2026
- Updated
- Nov 13, 2026
Why these Tags: an agent read the README and quoted it
- Android app from the readme:
名称：NP管理器
- Reverse engineering from the description:
Apk、dex、jar混淆和字符串加密
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 Nov 12, 2026: 1,876 stars on 2026-11-12.
Star History
190 days recorded, May 8, 2026 – Nov 13, 2026 (UTC). Net change +292 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/githubXiaowangzi/NP-Manager) Badge
[](https://awesomerepos.com/githubXiaowangzi/NP-Manager) Timeline
It gained stars on 139 of the 190 days recorded since May 8, 2026.
Its largest 7 days were Nov 6, 2026 to Nov 12, 2026: 35 stars.
In the 30 days to Nov 13, 2026 it got 84 stars, 110% more than in the 30 days before.
It had 1,593 stars before May 8, 2026 and has 1,885 stars now: 3,115 fewer than 5,000.
- Created on the Repository Host
- Largest star day recorded: +8 stars
- Release v3.2.9
- Release v3.2.8
- +8 stars in one day
- Release v3.2.10
- Release v3.2.11
- Latest push
- Entered the Repository Index: 1,876 stars on 2026-11-12
- +8 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 2 Observations, Nov 13, 2026 – Nov 14, 2026. Forks +1. AwesomeRepos saw a new push on 0 of 1 days.
- Nov 14, 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 reads the weekly commits, the changelog, and the community files each week for the 5,000 visible repositories with the most stars and for each rising repository. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 1 task for the maintainers of githubXiaowangzi/NP-Manager.
Improve the Health Facts of the GitHub repository githubXiaowangzi/NP-Manager. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/githubXiaowangzi/NP-Manager. A change to the repository can improve each of the item below. Each item gives the measured fact or score, and a task. 1. A licence Fact: GitHub finds no licence. Rule: GitHub finds a licence file. When GitHub cannot name the licence, the fact says so. Task: Ask me which licence to use. Do not choose one yourself. Then add the standard licence text as LICENSE at the root, so that GitHub can name the licence. Do not change the terms. Fill in only the fields of the template (for example the year and the copyright holder), and ask me for a value that you cannot verify. 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
2 of 4 checks (2 without data)-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-11-09, 5 days ago. Source
-
No data: Commits in the last 13 weeks
No data: AwesomeRepos has not read the weekly commits.
-
No data: Commits in 26 or more of the last 52 weeks
No data: AwesomeRepos has not read the weekly commits.
Releases
2 of 3 checks (1 without data)-
Yes: A release in the last 365 days
Newest release v3.2.11 on 2026-11-09, 5 days ago. 4 releases in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is v3.2.11. Source
-
No data: A changelog file at the root
No data: AwesomeRepos has not scanned this repository.
Security practice
0 of 1 check (1 without data)-
No data: A security policy
No data: AwesomeRepos has not scanned this repository.
AwesomeRepos has not asked OpenSSF Scorecard about this repository.
Community files
0 of 3 checks (2 without data)-
No: A licence
GitHub finds no licence. Source
-
No data: A contributing guide
No data: AwesomeRepos has not scanned this repository.
-
No data: A code of conduct
No data: AwesomeRepos has not scanned this repository.
Observations
Latest Observation, Nov 14, 2026: 1,885 stars, 125 forks, last push Nov 9, 2026, not archived. One of 2 Observations since Nov 13, 2026.