add: Coldfire security research library

[h3athen]

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/redcode-labs/Coldfire
• pkg.go.dev: https://pkg.go.dev/github.com/redcode-labs/Coldfire
• goreportcard.com: https://goreportcard.com/report/github.com/redcode-labs/Coldfire
• 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
  • Added a new public catalog entry, “Coldfire,” under the Security section, visible in the library listing.
  • Improves discoverability for users browsing security-related tools and resources.
  • No changes to features, behavior, settings, or error handling; this update is documentation-only.
  • No action required; the new entry appears automatically with the next content refresh.

[coderabbitai]

Walkthrough

A new entry named Coldfire was added to the Security section of README.md. No code or logic changes; documentation update only.

Changes

Cohort / File(s)	Summary
Documentation Update README.md	Added a new public catalog entry "Coldfire" under the Security section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nudge the README with a gentle paw,
A shiny name—Coldfire—joins the law.
No code to chase, no tests to run,
Just docs updated, nibble done.
Thump-thump! I hop with tidy pride,
A warmer burrow, neatly tied. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title clearly summarizes the primary change by stating that the Coldfire security research library is being added, which directly reflects the only change in the PR.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ 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 8cb5e86 and b6b24a5.

📒 Files selected for processing (1)

• README.md (1 hunks)

⏰ 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). (2)

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

🔇 Additional comments (1)

README.md (1)

2273-2273: Entry looks good; coverage and quality pages resolve, but README entry wasn’t found—please confirm it appears once in the correct README file.

---

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: FAIL (missing semver release)
• pkg.go.dev: OK
• goreportcard: OK (grade unknown)
• coverage: missing

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

[avelino]

Thanks for the contribution! Please add links to pkg.go.dev, Go Report Card and your code coverage report (Codecov/Coveralls). Also ensure the project has at least 5 months of history, a license, go.mod and a SemVer release. Once those items are provided we can proceed.

[avelino]

Hi @h3athen, the automated checks for this PR failed. Please review the build logs and fix the issues. Specifically, the PR Quality Checks/quality-check failed. Please address this and re-request a review.