aoguai / LiYing
LiYing is an automated photo processing program designed for automating the post-processing workflow of ID photos in general photo studios. | LiYing 是一套适用于自动化 完成一般照相馆后期证件照处理流程的照片自动处理的程序。
LiYing is an automated photo processing program designed for automating the post-processing workflow of ID photos in general photo studios. Machine translation by Claude Sonnet 5.5. A wrong translation? Report an error
- Stars
- 4,027 stars
- Forks
- 389 forks
- Language
- Python
- License
- AGPL-3.0
- Created
- Aug 3, 2024
- Last push
- Nov 8, 2026
- Updated
- Nov 11, 2026
Why these Tags: an agent read the README and quoted it
- Image processing library from the description:
LiYing is an automated photo processing program designed for automating the post-processing workflow of ID photos in general photo studios.
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 9, 2026: +195 stars in 7 days.
Star History
184 days recorded, May 12, 2026 – Nov 11, 2026 (UTC). Net change +878 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/aoguai/LiYing) Badge
[](https://awesomerepos.com/aoguai/LiYing) Timeline
It gained stars on 118 of the 184 days recorded since May 12, 2026.
Its largest 7 days were Sep 10, 2026 to Sep 16, 2026: 344 stars.
In the 30 days to Nov 11, 2026 it got 359 stars, 143% more than in the 30 days before.
It had 3,149 stars before May 12, 2026 and has 4,027 stars now: 973 fewer than 5,000.
- Created on the Repository Host
- Release LiYing_integration_20240806_Windows_v2
- Release v3.0.0
- Release v3.1.1
- Release v3.2.0
- Largest star day recorded: +148 stars
- +126 stars in one day
- Release v3.3.0
- +124 stars in one day
- Latest push
- Entered the Repository Index: +195 stars in 7 days
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 10, 2026 – Nov 12, 2026. Forks +1. AwesomeRepos saw a new push on 0 of 2 days.
- Nov 11, 2026: no new push
- 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 last read these facts from GitHub on Nov 11, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of aoguai/LiYing.
Improve the Health Facts of the GitHub repository aoguai/LiYing. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/aoguai/LiYing. 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-11). 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-11). 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
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-08, 4 days ago. Source
-
Yes: Commits in the last 13 weeks
3 commits on the default branch in the last 13 weeks (GitHub, 2026-11-11). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 6 of the last 52 weeks (GitHub, 2026-11-11). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 2
- 1
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 1
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 1
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 2
- 0
- 0
- 0
- 0
- 1
Releases
2 of 3 checks-
Yes: A release in the last 365 days
Newest release v3.3.0 on 2026-10-03, 40 days ago. 3 releases in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is v3.3.0. Source
-
No: A changelog file at the root
No changelog file at the root (GitHub, 2026-11-11).
Security practice
0 of 1 check-
No: A security policy
GitHub finds no security policy (GitHub, 2026-11-11).
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.
The GitHub dependency graph of this repository names 16 direct packages (scanned on Nov 11, 2026). Packages from 8 other repositories in the index are among them.
No scanned repository names a package from this repository.
Uses (in the index) · 8
-
PyPI: gradio
- numpy/numpy 33K
PyPI: numpy
- pallets/click 18K
PyPI: click
-
PyPI: pillow
-
GitHub Actions: actions/checkout
- ijl/orjson 8.3K
PyPI: orjson
- opencv/opencv-python 5.4K
PyPI: opencv-python
- tartley/colorama 3.8K
PyPI: colorama
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: 4,027 stars, 389 forks, last push Nov 8, 2026, not archived. One of 3 Observations since Nov 10, 2026.