nukeratframework / nukerat
A post exploitation framework for advanced Red Team operations
- Stars
- 232 stars
- Forks
- 57 forks
- Language
- TypeScript
- License
- GPL-3.0
- Created
- Nov 6, 2026
- Last push
- Nov 10, 2026
- Updated
- Nov 12, 2026
Why these Tags: an agent read the README and quoted it
- Penetration testing from the readme:
NukeRat is a post exploitation framework for advanced Red Team operations, focused on exploiting modern and complex environments.
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 11, 2026: +115 stars in 7 days.
Star History
3 days recorded, Nov 10, 2026 – Nov 12, 2026 (UTC). Net change +237 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/nukeratframework/nukerat) Badge
[](https://awesomerepos.com/nukeratframework/nukerat) Timeline
It gained stars on each of the 3 days recorded since Nov 10, 2026.
- Created on the Repository Host
- Reached 100 stars, 4 days after it was created
- Largest star day recorded: +145 stars, the same day as release 1.4.8-rc.5
- Release 1.4.8-rc.5
- Latest push
- Entered the Repository Index: +115 stars in 7 days
- +67 stars in one day
- +25 stars in one day
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 12, 2026 – Nov 13, 2026. Forks +12. AwesomeRepos saw a new push on 0 of 1 days.
- Nov 13, 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 13, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of nukeratframework/nukerat.
Improve the Health Facts of the GitHub repository nukeratframework/nukerat. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/nukeratframework/nukerat. 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-13). 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 code of conduct Fact: GitHub finds no code of conduct (GitHub, 2026-11-13). Rule: GitHub finds a code of conduct in the repository or in the owner's .github repository. Task: Add CODE_OF_CONDUCT.md at the root with the Contributor Covenant 2.1 text. Change only the contact method. 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-10, 3 days ago. Source
-
Yes: Commits in the last 13 weeks
52 commits on the default branch in the last 13 weeks (GitHub, 2026-11-13). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 1 of the last 52 weeks (GitHub, 2026-11-13). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 52
Releases
2 of 3 checks-
Yes: A release in the last 365 days
Newest release 1.4.8-rc.5 on 2026-11-10, 3 days ago. 1 release in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is 1.4.8-rc.5. Source
-
No: A changelog file at the root
No changelog file at the root (GitHub, 2026-11-13).
Security practice
1 of 1 check-
Yes: A security policy
GitHub finds a security policy (GitHub, 2026-11-13). Source
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
2 of 3 checksObservations
Latest Observation, Nov 13, 2026: 232 stars, 57 forks, last push Nov 10, 2026, not archived. One of 2 Observations since Nov 12, 2026.