Add wasmtime-go in WebAssembly

[TusharSharma811]

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 has a version-numbered release and a go.mod file.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc): https://github.com/bytecodealliance/wasmtime-go
• pkg.go.dev: https://pkg.go.dev/github.com/bytecodealliance/wasmtime-go
• goreportcard: https://goreportcard.com/report/github.com/bytecodealliance/wasmtime-go
• coverage: https://bytecodealliance.github.io/wasmtime-go/coverage.html#file0

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
  • Expanded the “Full stack web frameworks” list by adding “wasmtime-go,” describing it as Go bindings for the Wasmtime WebAssembly runtime with WASI support, JIT/AOT options, and secure, fast embedding. The entry appears adjacent to existing Wasmtime items. No other sections were modified, and there are no changes to public APIs or application behavior.

[github-actions]

Automated Quality Checks (from CONTRIBUTING minimum standards)

• Repo: FAIL (missing semver release)
• pkg.go.dev: OK
• goreportcard: missing
• coverage: missing

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

[coderabbitai]

Walkthrough

README updated to add a wasmtime-go entry under the “Full stack web frameworks” list, positioned after the existing Wasmtime-related line and before webapi. No other files or structures were modified.

Changes

Cohort / File(s)	Summary
Documentation README.md	Added list entry: wasmtime-go (Go bindings for Wasmtime WebAssembly runtime with WASI, JIT/AOT, embedding). Placement adjusted within the frameworks list; no deletions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• phanirithvij
• bukarumar147

Poem

A nibble of docs, a hop in the list,
wasmtime-go added—can’t be missed.
I twitch my nose, approve with delight,
JITs and WASI dance in the night.
Thump-thump! says the bunny, code kept tight. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly describes the primary change by noting the addition of the wasmtime-go library entry in the context of WebAssembly, making the intent of the pull request clear and directly related to the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
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.}

[avelino]

Hi @TusharSharma811, 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.