L0NE-6 / WorkBuddy-Daily
WorkBuddy 成长中心全能签到脚本 · App / 小程序 / 桌面任务自动化 · Token 永续 · 进度回读与自动补领 · 青龙/Actions
- Stars
- 693 stars
- Forks
- 293 forks
- Language
- Python
- License
- MIT
- Created
- Sep 12, 2026
- Last push
- Nov 19, 2026
- Updated
- Nov 19, 2026
Why these Tags: an agent read the README and quoted it
- Workflow automation from the description:
WorkBuddy 成长中心全能签到脚本 · App / 小程序 / 桌面任务自动化 · Token 永续 · 进度回读与自动补领 · 青龙/Actions
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 17, 2026: +104 stars in 7 days.
Star History
69 days recorded, Sep 12, 2026 – Nov 19, 2026 (UTC). Net change +700 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/L0NE-6/WorkBuddy-Daily) Badge
[](https://awesomerepos.com/L0NE-6/WorkBuddy-Daily) Timeline
It gained stars on each of the 69 days recorded since Sep 12, 2026.
Its largest 7 days were Nov 12, 2026 to Nov 18, 2026: 108 stars.
In the 30 days to Nov 19, 2026 it got 346 stars, 28% more than in the 30 days before.
- Created on the Repository Host
- Reached 100 stars, 11 days after it was created
- Largest star day recorded: +27 stars
- +20 stars in one day
- Reached 500 stars, 52 days after it was created
- Release v51
- Release v50
- Release v49
- +27 stars in one day
- Entered the Repository Index: +104 stars in 7 days
- Release v52
- Release v53
- Latest push
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 3 Observations, Nov 18, 2026 – Nov 20, 2026. Forks +13. AwesomeRepos saw a new push on 1 of 2 days.
- Nov 19, 2026: no new push
- Nov 20, 2026: 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 19, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 4 tasks for the maintainers of L0NE-6/WorkBuddy-Daily.
Improve the Health Facts of the GitHub repository L0NE-6/WorkBuddy-Daily. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/L0NE-6/WorkBuddy-Daily. A change to the repository can improve each of the 4 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 v53. 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 security policy Fact: GitHub finds no security policy (GitHub, 2026-11-19). 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. 3. A contributing guide Fact: GitHub finds no contributing guide (GitHub, 2026-11-19). 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). 4. A code of conduct Fact: GitHub finds no code of conduct (GitHub, 2026-11-19). 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
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-11-19, 1 day ago. Source
-
Yes: Commits in the last 13 weeks
197 commits on the default branch in the last 13 weeks (GitHub, 2026-11-19). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 10 of the last 52 weeks (GitHub, 2026-11-19). 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
- 0
- 0
- 0
- 0
- 24
- 44
- 29
- 30
- 5
- 16
- 16
- 14
- 8
- 11
Releases
2 of 3 checks-
Yes: A release in the last 365 days
Newest release v53 on 2026-11-19, 1 day ago. 10 or more releases in the last 365 days. Source
-
No: The newest release tag is a semantic version
The newest release tag is v53. Source
-
Yes: A changelog file at the root
CHANGELOG.md at the root (GitHub, 2026-11-19). Source
Security practice
0 of 1 check-
No: A security policy
GitHub finds no security policy (GitHub, 2026-11-19).
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
1 of 3 checks-
Yes: A licence
GitHub finds the licence MIT. Source
-
No: A contributing guide
GitHub finds no contributing guide (GitHub, 2026-11-19).
-
No: A code of conduct
GitHub finds no code of conduct (GitHub, 2026-11-19).
Observations
Latest Observation, Nov 20, 2026: 693 stars, 293 forks, last push Nov 19, 2026, not archived. One of 3 Observations since Nov 18, 2026.