leejet / stable-diffusion.cpp
Diffusion model(SD,Flux,Wan,Qwen Image,Z-Image,Minimax H3,...) inference in pure C/C++
- Stars
- 7,986 stars
- Forks
- 954 forks
- Language
- C++
- License
- MIT
- Created
- Aug 13, 2023
- Last push
- Nov 10, 2026
- Updated
- Nov 11, 2026
Why these Tags: an agent read the README and quoted it
- Image generation from the readme:
Generate an image with just one command
- Video generation from the readme:
- Video Models - Wan2.1/Wan2.2 - MiniMax-H3 - LTX-2.3/LTX-2.5 - HunyuanVideo 1.5 - LingBot-Video
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: 7,960 stars on 2026-11-10.
Star History
188 days recorded, May 8, 2026 – Nov 11, 2026 (UTC). Net change +2,123 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/leejet/stable-diffusion.cpp) Badge
[](https://awesomerepos.com/leejet/stable-diffusion.cpp) Timeline
It gained stars on each of the 188 days recorded since May 8, 2026.
Its largest 7 days were Sep 20, 2026 to Sep 26, 2026: 384 stars.
In the 30 days to Nov 11, 2026 it got 353 stars, 50% fewer than in the 30 days before.
It had 5,863 stars before May 8, 2026 and has 7,986 stars now: 2,014 fewer than 10,000.
- Created on the Repository Host
- Largest star day recorded: +162 stars
- +98 stars in one day
- +40 stars in one day
- Entered the Repository Index: 7,960 stars on 2026-11-10
- Release master-1086-465adf3
- Release master-1088-32d516c
- Release master-1087-f8417d0
- Release master-1081-e1ca5e8
- Release master-1080-a3f46b6
- 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 +5. AwesomeRepos saw a new push on 0 of 1 days.
- Nov 12, 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 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
Copies a prompt for a coding agent. It has 1 task for the maintainers of leejet/stable-diffusion.cpp.
Improve the Health Facts of the GitHub repository leejet/stable-diffusion.cpp. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/leejet/stable-diffusion.cpp. A change to the repository can improve each of the item 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 master-1086-465adf3. 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. 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
2 of 4 checks (2 without data)-
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, 1 day ago. Source
-
No data: Commits in the last 13 weeks
No data: AwesomeRepos has not read the weekly commits.
-
No data: Commits in 26 or more of the last 52 weeks
No data: AwesomeRepos has not read the weekly commits.
Releases
1 of 3 checks (1 without data)-
Yes: A release in the last 365 days
Newest release master-1086-465adf3 on 2026-11-10, 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 master-1086-465adf3. Source
-
No data: A changelog file at the root
No data: AwesomeRepos has not scanned this repository.
Security practice
0 of 1 check (1 without data)-
No data: A security policy
No data: AwesomeRepos has not scanned this repository.
AwesomeRepos has not asked OpenSSF Scorecard about this repository.
Community files
1 of 3 checks (2 without data)-
Yes: A licence
GitHub finds the licence MIT. Source
-
No data: A contributing guide
No data: AwesomeRepos has not scanned this repository.
-
No data: A code of conduct
No data: AwesomeRepos has not scanned this repository.
Dependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
The GitHub dependency graph of this repository names 15 direct packages (scanned on Nov 12, 2026). Packages from 1 other repository in the index are among them.
No scanned repository names a package from this repository.
Uses (in the index) · 1
-
GitHub Actions: actions/checkout
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 (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: 7,986 stars, 954 forks, last push Nov 10, 2026, not archived. One of 2 Observations since Nov 11, 2026.