djyde / dalibre
A lightweight Calibre alternative
- Stars
- 324 stars
- Forks
- 16 forks
- Language
- Go
- License
- Not reported
- Created
- Nov 8, 2026
- Last push
- Nov 11, 2026
- Updated
- Nov 11, 2026
Why these Tags: an agent read the README and quoted it
- E-book tool from the readme:
A calm, fast desktop library for e-books that reads and writes **calibre libraries**.
- MCP server from the readme:
Your own agents (Claude Code, Claude Desktop, Cursor…) can use the open library over MCP: search it, edit metadata, add books, and convert formats with their own tools.
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 10, 2026: +227 stars in 7 days.
Star History
4 days recorded, Nov 8, 2026 – Nov 11, 2026 (UTC). Net change +327 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/djyde/dalibre) Badge
[](https://awesomerepos.com/djyde/dalibre) Timeline
It gained stars on each of the 4 days recorded since Nov 8, 2026.
- Created on the Repository Host
- Reached 100 stars, 1 day after it was created
- Largest star day recorded: +277 stars, the same day as release v0.2.2
- Release v0.2.2
- Entered the Repository Index: +227 stars in 7 days
- +27 stars in one day
- Release v0.5.1
- Release v0.5.0
- Release v0.4.0
- Release v0.3.0
- +15 stars in one day
- 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 2 Observations, Nov 11, 2026 – Nov 12, 2026. Forks 0. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 12, 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 12, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 4 tasks for the maintainers of djyde/dalibre.
Improve the Health Facts of the GitHub repository djyde/dalibre. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/djyde/dalibre. 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. A security policy Fact: GitHub finds no security policy (GitHub, 2026-11-12). 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 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. 3. A contributing guide Fact: GitHub finds no contributing guide (GitHub, 2026-11-12). 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-12). 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-11, 1 day ago. Source
-
Yes: Commits in the last 13 weeks
61 commits on the default branch in the last 13 weeks (GitHub, 2026-11-12). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 1 of the last 52 weeks (GitHub, 2026-11-12). 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
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 61
Releases
3 of 3 checks-
Yes: A release in the last 365 days
Newest release v0.5.1 on 2026-11-10, 2 days ago. 9 releases in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is v0.5.1. Source
-
Yes: A changelog file at the root
CHANGELOG.md at the root (GitHub, 2026-11-12). Source
Security practice
0 of 1 check-
No: A security policy
GitHub finds no security policy (GitHub, 2026-11-12).
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
0 of 3 checks-
No: A licence
GitHub finds no licence. Source
-
No: A contributing guide
GitHub finds no contributing guide (GitHub, 2026-11-12).
-
No: A code of conduct
GitHub finds no code of conduct (GitHub, 2026-11-12).
Observations
Latest Observation, Nov 12, 2026: 324 stars, 16 forks, last push Nov 11, 2026, not archived. One of 2 Observations since Nov 11, 2026.