Chunyu33 / light-c
A free, minimalist, lightweight, and high-performance C-drive cleanup tool.
- Stars
- 3,449 stars
- Forks
- 146 forks
- Language
- Rust
- License
- OTHER
- Created
- Jan 26, 2026
- Last push
- Nov 10, 2026
- Updated
- Nov 12, 2026
Why these Tags: an agent read the README and quoted it
- System tweaker from the readme:
Review optional Windows system components and space-saving settings with clear safety warnings before applying changes
- Windows app from the readme:
LightC is a Windows desktop utility for safe junk cleanup, disk analysis, and system maintenance.
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 11, 2026: +110 stars in 7 days.
Star History
189 days recorded, May 8, 2026 – Nov 12, 2026 (UTC). Net change +3,427 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/Chunyu33/light-c) Badge
[](https://awesomerepos.com/Chunyu33/light-c) Timeline
It gained stars on 171 of the 189 days recorded since May 8, 2026.
Its largest 7 days were Jun 24, 2026 to Jun 30, 2026: 321 stars.
In the 30 days to Nov 12, 2026 it got 517 stars, 34% fewer than in the 30 days before.
- Created on the Repository Host
- Reached 100 stars, 146 days after it was created
- +72 stars in one day
- Reached 500 stars, 156 days after it was created
- Reached 1,000 stars, 175 days after it was created
- +68 stars in one day
- Largest star day recorded: +148 stars, 3 days after release v2.16.13
- Release v2.17.0
- Release v2.18.0
- Release v2.18.1
- Release v2.18.2
- Release v2.18.3
- Latest push
- Entered the Repository Index: +110 stars in 7 days
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 12, 2026 – Nov 13, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 1 days.
- Nov 13, 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 13, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 3 tasks for the maintainers of Chunyu33/light-c.
Improve the Health Facts of the GitHub repository Chunyu33/light-c. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/Chunyu33/light-c. A change to the repository can improve each of the 3 items below. Each item gives the measured fact or score, and a task. 1. A security policy Fact: GitHub finds no security policy (GitHub, 2026-11-13). 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. 2. A contributing guide Fact: GitHub finds no contributing guide (GitHub, 2026-11-13). Rule: GitHub finds a CONTRIBUTING file in the repository or in the owner's .github repository. Task: Add CONTRIBUTING.md at the root, in docs/, or in .github/. Tell a contributor how to set up the project, run the tests, and propose a change. Use the real commands of this repository (package scripts, Makefile, CI workflows). 3. A code of conduct Fact: GitHub finds no code of conduct (GitHub, 2026-11-13). Rule: GitHub finds a code of conduct in the repository or in the owner's .github repository. Task: Add CODE_OF_CONDUCT.md at the root with the Contributor Covenant 2.1 text. Change only the contact method. 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
4 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-11-10, 3 days ago. Source
-
Yes: Commits in the last 13 weeks
226 commits on the default branch in the last 13 weeks (GitHub, 2026-11-13). Source
-
Yes: Commits in 26 or more of the last 52 weeks
Commits in 36 of the last 52 weeks (GitHub, 2026-11-13). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 14
- 10
- 0
- 0
- 0
- 17
- 2
- 14
- 1
- 14
- 14
- 0
- 10
- 35
- 2
- 2
- 8
- 0
- 10
- 3
- 16
- 25
- 10
- 27
- 28
- 9
- 14
- 6
- 9
- 11
- 0
- 3
- 17
- 14
- 10
- 6
- 13
- 61
- 9
- 24
- 51
- 7
Releases
3 of 3 checks-
Yes: A release in the last 365 days
Newest release v2.18.3 on 2026-11-10, 3 days ago. 10 or more releases in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is v2.18.3. Source
-
Yes: A changelog file at the root
CHANGELOG.md at the root (GitHub, 2026-11-13). Source
Security practice
0 of 1 check-
No: A security policy
GitHub finds no security policy (GitHub, 2026-11-13).
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
1 of 3 checks-
Yes: A licence
GitHub finds a licence file, but cannot name the licence. Source
-
No: A contributing guide
GitHub finds no contributing guide (GitHub, 2026-11-13).
-
No: A code of conduct
GitHub finds no code of conduct (GitHub, 2026-11-13).
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 13, 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 13, 2026: 3,449 stars, 146 forks, last push Nov 10, 2026, not archived. One of 2 Observations since Nov 12, 2026.