nICEnnnnnnnLee / BilibiliDown

Star History

187 days recorded, May 9, 2026 – Nov 11, 2026 (UTC). Net change +638 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

[![Star History of nICEnnnnnnnLee/BilibiliDown](https://awesomerepos.com/nICEnnnnnnnLee/BilibiliDown/stars.svg)](https://awesomerepos.com/nICEnnnnnnnLee/BilibiliDown) Copy

Badge

[![AwesomeRepos](https://awesomerepos.com/nICEnnnnnnnLee/BilibiliDown/badge.svg)](https://awesomerepos.com/nICEnnnnnnnLee/BilibiliDown) Copy

Timeline

1. Jan 23, 2019 Created on the Repository Host
2. Nov 24, 2024 Release V6.37
3. Dec 22, 2024 Release V6.38
4. Feb 12, 2025 Release V6.39
5. Nov 23, 2025 Release V6.40
6. Apr 24, 2026 Release V6.41
7. May 31, 2026 +9 stars in one day
8. Jun 13, 2026 +10 stars in one day
9. Jul 6, 2026 Reached 5,000 stars, 2,721 days after it was created
10. Jul 10, 2026 Latest push
11. Jul 20, 2026 Largest star day recorded: +11 stars
12. Nov 10, 2026 Entered the Repository Index: 5,362 stars on 2026-11-10

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 11, 2026 – Nov 12, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 1 days.

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

Improve the Health Facts of the GitHub repository nICEnnnnnnnLee/BilibiliDown.

AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/nICEnnnnnnnLee/BilibiliDown. 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. The newest release tag is a semantic version
   Fact: The newest release tag is V6.41.
   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.

2. 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

Dependencies in the index

Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package (checked on Nov 3, 2026). 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 12, 2026: 5,365 stars, 455 forks, last push Jul 10, 2026, not archived. One of 2 Observations since Nov 11, 2026.