Add meds firewall to Security section

[cnaize]

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a coverage service link.
• The repo documentation has a goreportcard link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc): https://github.com/cnaize/meds
• pkg.go.dev: https://pkg.go.dev/github.com/cnaize/meds
• goreportcard.com: https://goreportcard.com/report/github.com/cnaize/meds
• coverage service link (codecov, coveralls, etc.):

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.

Thanks for your PR, you're awesome! 😎

Summary by CodeRabbit

• Documentation
  • README Security section updated to add a new library entry ("meds"), increasing the list of referenced libraries.
  • Change is additive: existing entries and documented behaviors remain unchanged.
  • No changes to exported/public APIs or runtime behavior documented.

[coderabbitai]

Walkthrough

A single-line, additive documentation change: the "meds" library entry was added to the Security section of README.md. No code, exports, or control flow were changed.

Changes

Cohort / File(s)	Summary
Documentation Update README.md	Added a new "meds" entry to the Security section (purely additive documentation change).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Files to spot-check:

• README.md — verify formatting and placement within the Security section.

Possibly related PRs

• Add SafeDep/vet to security libraries list #5836 — also adds a new library entry to the README Security section; similar documentation-only change.

Poem

A nibble of text, a tiny new thread,
🐇 meds hops in where the safe lists are spread.
No logic disturbed, just a friendly new name,
The README grows steady — a small, sunny claim.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "Add meds firewall to Security section" directly and accurately reflects the main change documented in both the raw summary and PR objectives. The title is specific and concise, clearly indicating what is being added (the meds firewall entry), where it is being added (the Security section of README.md), and the action being taken (Add). A teammate reviewing git history would immediately understand the primary purpose of this changeset without ambiguity or confusion.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.}

[github-actions]

Automated Quality Checks (from CONTRIBUTING minimum standards)

• Repo: OK
• pkg.go.dev: OK
• goreportcard: OK (grade unknown)
• coverage: missing

These checks are a best-effort automation and do not replace human review.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

2310-2310: Entry looks good; trim promotional wording and add required quality links in PR.

• Alphabetical order and period are correct.
• To keep tone neutral, drop “Modern,” from the description.

Apply this minimal tweak:

-- [meds](https://github.com/cnaize/meds) - Modern, lock-free NFQUEUE-based firewall written in Go with real-time filtering, TLS SNI/JA3 inspection, and Prometheus metrics.
+- [meds](https://github.com/cnaize/meds) - Lock-free NFQUEUE-based firewall with real-time filtering, TLS SNI/JA3 inspection, and Prometheus metrics.

Please include (in the PR body) the standard Awesome‑Go quality links for review:

• pkg.go.dev page
• Go Report Card
• Coverage service link (Codecov/Coveralls)
• Confirm tagged release, go.mod, and CI running tests

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 90f89e3 and b7349b3.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

README.md

📄 CodeRabbit inference engine (AGENTS.md)

README.md: When modifying the Awesome list, keep categories with at least three entries
Descriptions in the Awesome list must end with a period
Avoid promotional copy; keep descriptions concise and neutral in the Awesome list
Do not remove existing list content unless removal is requested and justified

Files:

• README.md

**/*.md

📄 CodeRabbit inference engine (AGENTS.md)

Keep documentation in English

Files:

• README.md

{README.md,COVERAGE.md}

📄 CodeRabbit inference engine (AGENTS.md)

Align rendered documentation (README.md, COVERAGE.md, etc.) with behavior changes in main.go or helper packages

Files:

• README.md