Add vibridi/gomock to Mock section

[vibridi]

Required links

Provide the links below. Our CI will automatically validate them.

• Forge link (github.com, gitlab.com, etc): https://github.com/vibridi/gomock
• pkg.go.dev: https://pkg.go.dev/github.com/vibridi/gomock/v3
• goreportcard.com: https://goreportcard.com/report/github.com/vibridi/gomock
• Coverage service link (codecov, coveralls, etc.): https://codecov.io/github/vibridi/gomock

Pre-submission checklist

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

Repository requirements

These are validated automatically by CI:

• The repo has a go.mod file and at least one SemVer release (vX.Y.Z).
• The repo has an open source license.
• The repo documentation has a pkg.go.dev link.
• The repo documentation has a goreportcard link (grade A- or better).
• The repo documentation has a coverage service link.

These are recommended and reported as warnings:

• The repo has a continuous integration process (GitHub Actions, etc.).
• CI runs tests that must pass before merging.

Pull Request content

These are validated automatically by CI:

• This PR adds/removes/changes only one package.
• The package has been added in alphabetical order.
• The link text is the exact project name.
• The description is clear, concise, non-promotional, and ends with a period.
• The link in README.md matches the forge link above.

Category quality

Note: new categories require a minimum of 3 packages.

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 they still meet the Quality Standards.

Please delete one of the following lines:

• I removed the following packages around my addition: (please give a short reason for each removal)

Removed gock https://github.com/h2non/gock as it appears it's no longer updated with open issues dating back years.

NOTE that by the same logic also uber-go/mock should be removed but there are two issues with it:

• it appears a conflict of interest since my package has a similar name
• it's unclear whether the awesome-go entry refers to the entire repository or to a sub-package, and it's also unclear whether the open issues refer to the same thing linked in awesome-go

Thanks for your PR, you're awesome! 😎

[github-actions]

Automated Quality Checks

Required checks

✅ Repo: accessible, has go.mod and SemVer release
✅ pkg.go.dev: OK
✅ Go Report Card: OK (grade unknown)

Additional checks

✅ License: MIT
✅ Maturity: repo has 5+ months of history
✅ CI/CD: GitHub Actions workflows detected
✅ README: present
⚠️ Coverage: missing from PR body

How to fix: Add a coverage service link to your PR description:

Coverage: https://app.codecov.io/gh/your-org/your-project

Popular options: [Codecov](https://codecov.io), [Coveralls](https://coveralls.io). Integrate one with your CI to track coverage automatically.


_These checks are automated and do not replace maintainer review. See [CONTRIBUTING.md](https://github.com/avelino/awesome-go/blob/main/CONTRIBUTING.md) for full guidelines._

---

## PR Diff Validation

### Content checks

✅ **Files changed**: only README.md
✅ **Link consistency**: README link matches forge link in PR body
✅ **Link text**: matches repository name
✅ **Description**: ends with punctuation
✅ **Description tone**: no promotional language detected
✅ **Category size**: Mock has 21 items

### Warnings

⚠️ **Changes**: 1 added + 1 removed (update or move — please confirm in PR description)


_Automated diff validation — does not replace maintainer review._
<!-- Sticky Pull Request Commentpr-quality-check -->