AIFengheshu / Plug-play-modules
2025年全网最全即插即用模块，免费分享！CVPR2025，AAAI2025，ICLR2025，TNNLS2025，arXiv2025......包含人工智能全领域（机器学习、深度学习等），适用于图像分类、目标检测、实例分割、语义分割、全景分割、姿态识别、医学图像分割、视频目标分割、图像抠图、图像编辑、单目标跟踪、多目标跟踪、行人重识别、RGBT、图像去噪、去雨、去雾、去阴影、去模糊、超分辨率、去反光、去摩尔纹、图像恢复、图像修复、高光谱图像恢复、图像融合、图像上色、高动态范围成像、视频与图像压缩、3D点云、3D目标检测、3D语义分割、3D姿态识别等各类计算机视觉和图像处理任务，以及自然语言处理、大语言模型、多模态等其他各类人工智能相关任务。持续更新中......
- Stars
- 1,657 stars
- Forks
- 125 forks
- Language
- Python
- License
- Not reported
- Created
- Oct 9, 2024
- Last push
- May 24, 2025
- Updated
- Nov 14, 2026
Why these Tags: an agent read the README and quoted it
- Paper implementation from the readme:
2025年即插即用代码模块与论文解读汇总
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 12, 2026: 1,657 stars on 2026-11-12.
Star History
181 days recorded, May 18, 2026 – Nov 14, 2026 (UTC). Net change +151 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/AIFengheshu/Plug-play-modules) Badge
[](https://awesomerepos.com/AIFengheshu/Plug-play-modules) Timeline
It gained stars on 110 of the 181 days recorded since May 18, 2026.
Its largest 7 days were Jun 18, 2026 to Jun 24, 2026: 12 stars.
In the 30 days to Nov 14, 2026 it got 29 stars, 38% more than in the 30 days before.
It had 1,506 stars before May 18, 2026 and has 1,657 stars now: 3,343 fewer than 5,000.
- Created on the Repository Host
- Latest push
- Largest star day recorded: +4 stars
- +3 stars in one day
- +3 stars in one day
- Entered the Repository Index: 1,657 stars on 2026-11-12
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 13, 2026 – Nov 15, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 2 days.
- Nov 14, 2026: no new push
- Nov 15, 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 2 tasks for the maintainers of AIFengheshu/Plug-play-modules.
Improve the Health Facts of the GitHub repository AIFengheshu/Plug-play-modules. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/AIFengheshu/Plug-play-modules. 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 release in the last 365 days Fact: No GitHub release (read on 2026-11-12). Rule: The newest published GitHub release (a pre-release counts; a draft does not) is 365 days old or less. A repository that publishes only tags, or only to a package registry, has no GitHub release. The release refresh reads the 10 newest releases after each push to the repository, and at least each 30 days. The index refresh reads the date of the last push each day. Task: Prepare a release, but do not publish it. Find the changes since the newest release, propose the next semantic version and the release notes, and ask me to publish the GitHub release. If nothing changed since the newest release, skip this item. If the project publishes only to a package registry, add a CI step that also makes a GitHub release for each version tag. 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. 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
1 of 4 checks (2 without data)-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
No: A push in the last 90 days
Last push on 2025-05-24, 540 days 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
0 of 3 checks (2 without data)-
No: A release in the last 365 days
No GitHub release (read on 2026-11-12). Source
-
No data: The newest release tag is a semantic version
No data: no release.
-
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
0 of 3 checks (2 without data)-
No: A licence
GitHub finds no licence. 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.
Observations
Latest Observation, Nov 15, 2026: 1,657 stars, 125 forks, last push May 24, 2025, not archived. One of 3 Observations since Nov 13, 2026.