Threekiii / Awesome-POC
一个漏洞 PoC 知识库。A knowledge base for vulnerability PoCs(Proof of Concept), with 1k+ vulnerabilities.
A knowledge base for vulnerability PoCs(Proof of Concept), with 1k+ vulnerabilities. Machine translation by Claude Sonnet 5.5. A wrong translation? Report an error
- Stars
- 5,253 stars
- Forks
- 1,058 forks
- Language
- Java
- License
- Not reported
- Created
- Feb 20, 2022
- Last push
- May 11, 2026
- Updated
- Nov 11, 2026
Admitted to the Repository Index on Nov 10, 2026: 5,249 stars on 2026-11-10.
Star History
185 days recorded, May 11, 2026 – Nov 11, 2026 (UTC). Net change +348 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/Threekiii/Awesome-POC) Badge
[](https://awesomerepos.com/Threekiii/Awesome-POC) Timeline
It gained stars on 147 of the 185 days recorded since May 11, 2026.
Its largest 7 days were Jul 20, 2026 to Jul 26, 2026: 24 stars.
In the 30 days to Nov 11, 2026 it got 52 stars, 93% more than in the 30 days before.
- Created on the Repository Host
- Release v1.0: awesome-poc
- Release v2.0
- Latest push
- Largest star day recorded: +6 stars
- +6 stars in one day
- Reached 5,000 stars, 1,578 days after it was created
- +6 stars in one day
- Entered the Repository Index: 5,249 stars on 2026-11-10
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 +1. 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 2 tasks for the maintainers of Threekiii/Awesome-POC.
Improve the Health Facts of the GitHub repository Threekiii/Awesome-POC. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/Threekiii/Awesome-POC. 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. The newest release tag is a semantic version Fact: The newest release tag is v2.0. 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 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 2026-05-11, 185 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
1 of 3 checks (1 without data)-
Yes: A release in the last 365 days
Newest release v2.0 on 2026-01-04, 312 days ago. 1 release in the last 365 days. Source
-
No: The newest release tag is a semantic version
The newest release tag is v2.0. 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
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 12, 2026: 5,253 stars, 1,058 forks, last push May 11, 2026, not archived. One of 2 Observations since Nov 11, 2026.