Add trufflehog to Security section

[viragz158]

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/trufflesecurity/trufflehog
• pkg.go.dev: https://pkg.go.dev/github.com/trufflesecurity/trufflehog/v3@v3.90.11
• goreportcard.com: https://goreportcard.com/report/github.com/trufflesecurity/trufflehog/v3
• coverage service link (codecov, coveralls, etc.): https://app.codecov.io/github/viragz158/trufflehog (Not sure why it reports 0%)

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.
• I removed the following packages around my addition: (please give a short reason for each removal)

Thanks for your PR, you're awesome! 😎

Summary by CodeRabbit

• Documentation
  • Updated the Security section with a new library entry.

[coderabbitai]

Walkthrough

Adds a new entry for trufflehog under the Security category in the README, positioned alphabetically between themis and urusai. No existing entries or descriptions were modified.

Changes

Cohort / File(s)	Change Summary
Documentation Update README.md	Added trufflehog entry to the Security section of the library list

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single-line addition to documentation
• No code logic changes
• Straightforward alphabetical ordering

Poem

🐰 A fuzzy friend hops through the list so neat,
Adding trufflehog—security's sweet treat!
Between themis and urusai it finds its place,
Documentation blooms with trusty grace. ✨

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
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Add trufflehog to Security section" directly and accurately describes the main change in the changeset, which is confirmed by the raw summary stating "Adds a new entry for trufflehog under the Security category." The title is concise (5 words), specific, and avoids vague or generic language. It clearly communicates what was changed and where, making it easy for someone reviewing the repository history to understand the primary modification without additional context.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 Recent 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 6e5c254.

📒 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

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (20)

• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: quality
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: quality
• GitHub Check: quality

🔇 Additional comments (1)

README.md (1)

2326-2326: LGTM: entry conforms to Awesome Go list rules.

• Alphabetical placement between “themis” and “urusai” is correct.
• Description is concise, neutral, and ends with a period.
• No existing content removed.

---

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.