al0ne / LinuxCheck
Linux应急处置/信息搜集/漏洞检测工具，支持基础配置/网络流量/任务计划/环境变量/用户信息/Services/bash/恶意文件/内核Rootkit/SSH/Webshell/挖矿文件/挖矿进程/供应链/服务器风险等13类70+项检查
- Stars
- 2,116 stars
- Forks
- 428 forks
- Language
- Shell
- License
- MIT
- Created
- Dec 17, 2018
- Last push
- Jun 19, 2024
- Updated
- Nov 12, 2026
Why these Tags: an agent read the README and quoted it
- Digital forensics from the description:
Linux应急处置/信息搜集/漏洞检测工具
- Vulnerability scanner from the description:
恶意文件/内核Rootkit/SSH/Webshell/挖矿文件/挖矿进程/供应链/服务器风险等13类70+项检查
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: 2,116 stars on 2026-11-12.
Star History
190 days recorded, May 8, 2026 – Nov 13, 2026 (UTC). Net change +61 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/al0ne/LinuxCheck) Badge
[](https://awesomerepos.com/al0ne/LinuxCheck) Timeline
It gained stars on 53 of the 190 days recorded since May 8, 2026.
Its largest 7 days were May 23, 2026 to May 29, 2026: 5 stars.
In the 30 days to Nov 13, 2026 it got 8 stars, 11% fewer than in the 30 days before.
It had 2,055 stars before May 8, 2026 and has 2,116 stars now: 2,884 fewer than 5,000.
- Created on the Repository Host
- Release V2.2: 更新LinuxCheck检测功能
- Release V2.3: 更新LinuxCheck检测功能
- Release V3.0: 更新LinuxCheck脚本
- Latest push
- Largest star day recorded: +2 stars
- +2 stars in one day
- +2 stars in one day
- Entered the Repository Index: 2,116 stars on 2026-11-12
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 0. 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 2 tasks for the maintainers of al0ne/LinuxCheck.
Improve the Health Facts of the GitHub repository al0ne/LinuxCheck. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/al0ne/LinuxCheck. 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: Newest release V3.0 on 2024-05-09, 919 days ago. 0 releases in the last 365 days. 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. The newest release tag is a semantic version Fact: The newest release tag is V3.0. Rule: The tag of the newest release has the form 1.2.3 or v1.2.3, with an optional pre-release or build part. There is no data when the repository has no release. Task: Make the next release tag a semantic version (1.2.3 or v1.2.3). Do not change or delete a published tag. If a release tool makes the tags, configure it for semantic versions, and write the version scheme in the contributing guide. 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
1 of 4 checks (2 without data)-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
No: A push in the last 90 days
Last push on 2024-06-19, 878 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
0 of 3 checks (1 without data)-
No: A release in the last 365 days
Newest release V3.0 on 2024-05-09, 919 days ago. 0 releases in the last 365 days. Source
-
No: The newest release tag is a semantic version
The newest release tag is V3.0. 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
1 of 3 checks (2 without data)-
Yes: A licence
GitHub finds the licence MIT. 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.
Dependencies 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 14, 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 14, 2026: 2,116 stars, 428 forks, last push Jun 19, 2024, not archived. One of 2 Observations since Nov 13, 2026.