CroqueMr / libreelec-CB1
LibreELEC with High Quality Dolby Vision & HDR10+ support for Intel, AMD, Nvidia, and more
- Stars
- 340 stars
- Forks
- 23 forks
- Language
- C
- License
- Not reported
- Created
- Sep 25, 2026
- Last push
- Nov 16, 2026
- Updated
- Nov 17, 2026
Why these Tags: an agent read the README and quoted it
- Linux distribution from the description:
LibreELEC x86_64 with Dolby Vision support for Intel, AMD, and Nvidia.
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 Oct 26, 2026: +118 stars in 7 days.
Star History
53 days recorded, Sep 25, 2026 – Nov 16, 2026 (UTC). Net change +342 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/CroqueMr/libreelec-CB1) Badge
[](https://awesomerepos.com/CroqueMr/libreelec-CB1) Timeline
It gained stars on 51 of the 53 days recorded since Sep 25, 2026.
Its largest 7 days were Oct 24, 2026 to Oct 30, 2026: 162 stars.
- Created on the Repository Host
- Release R1.0.0-Beta4
- Release R1.0.0-Beta5
- Reached 100 stars, 29 days after it was created
- +24 stars in one day
- Largest star day recorded: +91 stars
- Entered the Repository Index: +118 stars in 7 days
- +17 stars in one day
- Release R1.0.0-RC1
- Release untagged-27906d2c4291ba113414: R1.0.0 RC2
- Release R1.0.0-RC3
- Latest push
- Renamed from CroqueMr/libreelec-x86-DV to CroqueMr/libreelec-CB1
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 22 Observations, Oct 27, 2026 – Nov 17, 2026. Forks +14. AwesomeRepos saw a new push on 18 of 21 days.
- Oct 28, 2026: no new push
- Oct 29, 2026: new push
- Oct 30, 2026: new push
- Oct 31, 2026: new push
- Nov 1, 2026: new push
- Nov 2, 2026: new push
- Nov 3, 2026: new push
- Nov 4, 2026: new push
- Nov 5, 2026: new push
- Nov 6, 2026: new push
- Nov 7, 2026: no new push
- Nov 8, 2026: new push
- Nov 9, 2026: no new push
- Nov 10, 2026: new push
- Nov 11, 2026: new push
- Nov 12, 2026: new push
- Nov 13, 2026: new push
- Nov 14, 2026: new push
- Nov 15, 2026: new push
- Nov 16, 2026: new push
- Nov 17, 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 CroqueMr/libreelec-CB1.
Improve the Health Facts of the GitHub repository CroqueMr/libreelec-CB1. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/CroqueMr/libreelec-CB1. 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 R1.0.0-RC4-Preview. 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-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. 3. 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. 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-16, 0 days ago. Source
-
Yes: Commits in the last 13 weeks
378 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 7 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
- 59
- 13
- 8
- 36
- 114
- 48
- 100
Releases
2 of 3 checks-
Yes: A release in the last 365 days
Newest release R1.0.0-RC4-Preview on 2026-11-07, 10 days 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 R1.0.0-RC4-Preview. Source
-
Yes: A changelog file at the root
CHANGELOG 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
1 of 3 checksDependencies 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 6, 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 17, 2026: 340 stars, 23 forks, last push Nov 16, 2026, not archived. One of 22 Observations since Oct 27, 2026.