[Enhancement] Backfill tool tables in .md files with new 8-column schema (Creation Date + Stars)

[jacob-kraniak]

Description of the Enhancement

Following the recent update to our tool table schema (see TOOL-TABLE-SCHEMA.md), we now have this extended format:

| Name | Vendor/Webpage | GitHub Repo | Brief Description | Tags | Latest Commit | Creation Date | Stars |

The new columns are:

• Creation Date — repo creation date (YYYY-MM-DD) for GitHub projects; earliest known release year for legacy/non-GitHub tools (especially useful for 1990s–2000s classics)
• Stars — current GitHub star count (e.g. 35.4k, 812) with optional "as of YYYY-MM" note; use — for non-GitHub projects

Current status

• The schema file has been updated with these columns and rules (commit ~March 2026).
• Most (if not all) existing tool tables in README.md and category .md files still use the old 6-column format.
• No widespread migration has occurred yet.

Goal
Convert existing tool tables to the new 8-column format, and backfill the new columns where data is available. This will:

• Provide historical context for foundational/legacy tools
• Give newcomers a quick signal of community adoption & trust via star counts
• Keep tables consistent and future-proof

Help needed
Looking for assistance (one-time or ongoing) to:

1. Identify all .md files containing tool tables (primarily README.md sections + any split category files under documentation/, tools/, etc.)
2. Convert those tables from 6 → 8 columns (add empty/new columns at the end for now)
3. Backfill Creation Date and Stars for as many entries as possible:
   • Use GitHub repo "About" section or API for creation date & stars
   • For very old projects (pre-GitHub), use first public release year (from Wikipedia, old homepages, etc.)
   • Note approximate dates with ~ if exact unknown (e.g. ~1991)
   • Add "as of 2026-03" or similar for star counts (can be refreshed later)
4. Leave new columns as — if data can't be found quickly

Priority sections to start with (easiest & highest value)

• Sysadmin/DevOps → text-editors (many classics like Vim, Emacs, nano)
• Sysadmin/DevOps → terminal-multiplexers (tmux, screen)
• Sysadmin/DevOps → system-monitoring-tracing
• Security → defensive / blue-team tools
• Any section heavy on long-lived Unix/CLI tools

How to contribute

1. Pick a section or small group of tools
2. Update the table(s) in a new branch
3. Follow the exact rules in TOOL-TABLE-SCHEMA.md
4. Submit a PR with before/after screenshots or diff for review

No strict deadline — even partial progress (e.g. one category) is very welcome. If you're new to the repo, feel free to ask questions here or start with just 5–10 rows as a test.

Thanks in advance to anyone who helps make this repo more informative for beginners and respects the history of these amazing tools!

Labels: enhancement, good first issue (if you want to mark some parts that way), maintenance