Update python dep

[DefinetlyNotAI]

Updated dependencies and fixed security vuln in some dependencies

Summary by CodeRabbit

• Documentation

  • Streamlined README with cleaner formatting, simplified section headings, and improved visual hierarchy for better readability and navigation.

• Chores

  • Updated project dependencies to latest compatible versions for enhanced performance and security.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Workflow configuration updates include formatting changes and parameter renaming for GitHub Actions. README documentation gets a cleanup by removing emoji decorations. Python dependencies are upgraded to newer versions across multiple packages.

Changes

Cohort / File(s)	Summary
Workflow Configuration .github/workflows/greetings.yml	Trigger formatting corrected; harden-runner step version pin comment removed; First Interaction action parameters renamed from kebab-case to snake_case (e.g., repo-token → repo_token); explicit step name added
Documentation Cleanup README.md	Removed emoji decorations from section titles and headings; simplified heading formatting throughout document; minor wording adjustments to installation and usage sections
Dependency Updates requirements.txt	Updated 6 packages to newer versions: psutil (6.1.1 → 7.2.1), aiofiles (24.1.0 → 25.1.0), tqdm (4.66.6 → 4.67.1), prettytable (3.15.1 → 3.17.0), networkx (3.2.1 → 3.6.1), cryptography (44.0.2 → 46.0.3); scapy upgraded to 2.7.0rc1

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Suggested labels

type/Code, type/Documentation

Poem

🔧 Workflows get cleaned, dependencies rise,
Emojis fade away before our eyes,
Snake_case flows where kebabs used to be,
Each version bumped up, modern and free! 📦✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update python dep' is vague and incomplete—it uses abbreviations without clarity (dep could mean dependency, deploy, or deprecate) and doesn't specify which dependencies were updated or why.	Make the title more descriptive, like 'Update Python dependencies for security and compatibility' or 'Update Python packages to latest versions'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch req-update

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This pull request updates Python dependencies across the project, ostensibly to address security vulnerabilities, and removes emoji characters from the README.md documentation for a cleaner presentation.

Changes:

• Updated 9 Python package versions in requirements.txt
• Removed emoji characters from README.md section headers and content

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
requirements.txt	Updated versions for psutil, aiofiles, tqdm, prettytable, networkx, cryptography, scapy, and configparser
README.md	Removed emoji characters from headers and inline text throughout the documentation

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@requirements.txt`:
- Line 19: The requirements entry uses a release candidate: replace the scapy
version specifier "scapy~=2.7.0rc1" with the stable release "scapy~=2.7.0" in
requirements.txt so the project depends on the official 2.7.0 release instead of
the RC.

🧹 Nitpick comments (1)

.github/workflows/greetings.yml (1)

16-16: Version tracking info is gone.

Yo heads up - you removed the version comment (like # v2.14.0) from the action reference. It's not gonna break anything, but having that comment made it super easy to know what version you're pinning to without looking up the SHA. Consider keeping version comments for future you!

📝 Suggested format

-        uses: step-security/harden-runner@20cf305ff2072d973412fa9b1e3a4f227bda3c76
+        uses: step-security/harden-runner@20cf305ff2072d973412fa9b1e3a4f227bda3c76 # v2.x.x