mirror of
https://github.com/Z4nzu/hackingtool
synced 2026-05-23 17:08:25 +00:00
06245219c9
README.md:
- Modern centered header with full badge row
- Stats banner: 17 categories, 150+ tools
- What's new as a comparison table
- Tool category table with per-category counts
- Complete tool listing with star markers for new tools
- Contributing section with enforced title formats for issues and PRs
- Star History chart (Z4nzu/hackingtool)
- Cleaned up Installation, Requirements, Social sections
README_template.md:
- Full redesign matching README.md layout
- {{toc}} and {{tools}} placeholders preserved for generate_readme.py
- Contributing section with title format rules embedded in template
.github/ISSUE_TEMPLATE/bug_report.md:
- Remove irrelevant browser/smartphone sections
- Add tool name, category, error output, environment table
.github/ISSUE_TEMPLATE/feature_request.md:
- Tighten to 4 focused fields, note tool additions use separate template
.github/ISSUE_TEMPLATE/tool_request.md (new):
- Structured template for new tool suggestions
- Required fields: name, URL, category, OS, install/run commands, reason
- Enforced title format: [Tool Request] ToolName - Category
.github/PULL_REQUEST_TEMPLATE.md (new):
- PR checklist for new tool additions and other change types
- Enforced title format: [New Tool] / [Fix] / [Improve]
- All required class fields listed as checklist items
.github/workflows/lint_python.yml:
- actions/checkout v3 -> v4, setup-python v4 -> v5
- python-version: 3.x -> 3.12 (project requires 3.10+)
- ruff target-version: py37 -> py310
- ruff --show-source -> --output-format=full (updated flag name)
- Remove deprecated safety check command
.github/workflows/test_install.yml:
- actions/checkout v3 -> v4, setup-python v4 -> v5
- python-version: 3.x -> 3.12
- Replace fragile matrix of hard-coded menu numbers with
two simple smoke tests: launch+quit, and navigate+back
43 lines
1.4 KiB
Markdown
43 lines
1.4 KiB
Markdown
---
|
|
name: Tool Request
|
|
about: Suggest a new tool to be added to hackingtool
|
|
title: "[Tool Request] <ToolName> — <Category>"
|
|
labels: tool-request
|
|
assignees: ''
|
|
---
|
|
|
|
<!--
|
|
TITLE FORMAT (required): [Tool Request] ToolName — Category
|
|
Example: [Tool Request] Subfinder — Information Gathering
|
|
Issues without this title format may be closed without review.
|
|
-->
|
|
|
|
## Tool Details
|
|
|
|
| Field | Value |
|
|
|---|---|
|
|
| **Tool name** | <!-- e.g. Subfinder --> |
|
|
| **GitHub URL** | <!-- e.g. https://github.com/projectdiscovery/subfinder --> |
|
|
| **Category** | <!-- Choose one: Anonymously Hiding / Information Gathering / Wordlist Generator / Wireless Attack / SQL Injection / Phishing / Web Attack / Post Exploitation / Forensics / Payload Creation / Exploit Framework / Reverse Engineering / DDOS / RAT / XSS / Steganography / Other --> |
|
|
| **Supported OS** | <!-- Linux / macOS / Both --> |
|
|
| **Language** | <!-- Python / Go / Rust / C / Bash / etc. --> |
|
|
| **Install method** | <!-- pip / go install / apt / git clone / etc. --> |
|
|
|
|
## Why should it be added?
|
|
<!-- What does this tool do that isn't already covered? Min 2 sentences. -->
|
|
|
|
## Install Command
|
|
```bash
|
|
# paste the install command(s) here
|
|
```
|
|
|
|
## Run Command
|
|
```bash
|
|
# paste the run/usage command here
|
|
```
|
|
|
|
## Is the tool actively maintained?
|
|
<!-- Yes / No — link to last commit or release date -->
|
|
|
|
## Additional Notes
|
|
<!-- Anything else the maintainer should know -->
|