Straw1997 / renderdocBread
RenderDoc soco's edit version base 1.36
- Stars
- 191 stars
- Forks
- 45 forks
- Language
- C++
- License
- MIT
- Created
- Feb 2, 2026
- Last push
- Nov 8, 2026
- Updated
- Nov 8, 2026
Why these Tags: an agent read the README and quoted it
- Debugger from the readme:
可视化查看中间计算结果，动态调整参数，定位画面差异。
(machine translation by Claude Sonnet 5.5:Visually inspect intermediate calculation results, dynamically adjust parameters, and locate differences in the rendered image.
) - Windows app from the readme:
在 Releases 下载 Windows x64 完整便携版和 SHA-256 校验文件。解压后运行 `RenderDocBread.exe`。
(machine translation by Claude Sonnet 5.5:Download the complete portable Windows x64 version and the SHA-256 checksum file from Releases. After extracting, run `RenderDocBread.exe`.
)
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 7, 2026: +162 stars in 7 days.
Star History
57 days recorded, Sep 13, 2026 – Nov 8, 2026 (UTC). Net change +199 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/Straw1997/renderdocBread) Badge
[](https://awesomerepos.com/Straw1997/renderdocBread) Timeline
It gained stars on 6 of the 57 days recorded since Sep 13, 2026.
Its largest 7 days were Nov 2, 2026 to Nov 8, 2026: 198 stars.
- Created on the Repository Host
- +61 stars in one day
- Reached 100 stars, 276 days after it was created
- Largest star day recorded: +84 stars, the same day as release v1.13.126
- Release v1.13.126
- Release v1.13.125
- Release v1.13.124
- +21 stars in one day
- Release v1.13.127
- Entered the Repository Index: +162 stars in 7 days
- Release v1.13.128
- 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 8, 2026 – Nov 9, 2026. Forks +2. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 9, 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 9, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of Straw1997/renderdocBread.
Improve the Health Facts of the GitHub repository Straw1997/renderdocBread. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/Straw1997/renderdocBread. 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. A changelog file at the root Fact: No changelog file at the root (GitHub, 2026-11-09). Rule: The root of the default branch has a file named CHANGELOG, CHANGES, HISTORY, NEWS, RELEASE, or RELEASES, with no extension or with .md, .markdown, .rst, .txt, or .adoc. Release notes on GitHub releases do not count. Task: Add CHANGELOG.md at the root of the default branch. Write one section for each published release, newest first, from the GitHub releases, the Git tags, and the commit history. Do not invent changes. If the project uses a release tool (for example Changesets, release-please, or semantic-release), configure it to update this file for each release. 2. A security policy Fact: GitHub finds no security policy (GitHub, 2026-11-09). 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. 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
4 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-08, 1 day ago. Source
-
Yes: Commits in the last 13 weeks
55 commits on the default branch in the last 13 weeks (GitHub, 2026-11-09). Source
-
Yes: Commits in 26 or more of the last 52 weeks
Commits in 28 of the last 52 weeks (GitHub, 2026-11-09). Source
- 48
- 28
- 22
- 19
- 35
- 6
- 1
- 6
- 16
- 16
- 26
- 30
- 31
- 26
- 7
- 19
- 19
- 30
- 9
- 15
- 8
- 11
- 32
- 10
- 4
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 3
- 0
- 10
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 42
Releases
2 of 3 checks-
Yes: A release in the last 365 days
Newest release v1.13.128 on 2026-11-08, 1 day ago. 8 releases in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is v1.13.128. Source
-
No: A changelog file at the root
No changelog file at the root (GitHub, 2026-11-09).
Security practice
0 of 1 check-
No: A security policy
GitHub finds no security policy (GitHub, 2026-11-09).
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
3 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 9, 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 9, 2026: 191 stars, 45 forks, last push Nov 8, 2026, not archived. One of 2 Observations since Nov 8, 2026.