chore: update tools.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Bug Fixes

  • Corrected tool metadata including names, descriptions, repository URLs, and categorization across multiple tools and generators.
  • Fixed ownership and commercial flag assignments for various tools.
  • Updated language and technology designations for code generators and templates to reflect accurate information.

• Chores

  • Reorganized tool entries for improved consistency and accuracy in the tool registry.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	13f2e68
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/6948943acb8ee0000817330a
😎 Deploy Preview	https://deploy-preview-4754--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

Configuration files updated with tag name swaps in all-tags.json, extensive tool metadata reorganization in tools-automated.json (including new Golang AsyncAPI Code Generator entry), and URL/description corrections in tools.json.

Changes

Cohort / File(s)	Summary
Language tag name swaps config/all-tags.json	Two adjacent language entry pairs swapped their "name" fields: AsyncAPI Generator ↔ AsyncAPI CLI and SmartPaste ↔ JetBrains. No structural changes to colors, borders, or overall hierarchy.
Tool metadata reorganization and new entry config/tools-automated.json	Extensive reshuffling: Code-first tools (Zod Sockets ↔ AsyncAPI.Net), new Golang AsyncAPI Code Generator entry, GitHub Actions entries (Generator ↔ CLI), IDE Extensions/Editor entries (jAsyncAPI/VSCode), AsyncAPI Generator Templates (HTML ↔ Java ↔ Spring), and category/language/technology/ownership flag updates across DSL, Frameworks, Bundlers, and Validators sections.
Tool repository URLs and descriptions config/tools.json	Repository URLs and descriptions corrected for AsyncAPI Studio entries and HTML Template entries; swapped/toggled between alternate sources and description values across multiple tool blocks.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

• config/tools-automated.json requires careful attention: extensive reshuffling across multiple sections (Code-first tools, Code Generators, IDE Extensions, Generator Templates, GitHub Actions, Bundlers, Validators) with dozens of entry swaps, category/technology/ownership flag changes, and one new entry introduction—each swap and metadata change should be verified for correctness.
• Cross-file consistency should be checked between all-tags.json, tools-automated.json, and tools.json to ensure swapped entries align and no orphaned references exist.
• The repetitive nature of swaps (name/repo/category pairs toggling) reduces per-change review complexity, but the sheer volume demands systematic verification.

Possibly related PRs

• chore: update tools.json #4429 — Both PRs modify SmartPaste and JetBrains name swap in config/all-tags.json.
• chore: update tools.json #4399 — Both PRs make overlapping metadata edits to config/tools-automated.json and config/tools.json, including tool entry swaps and Golang AsyncAPI Code Generator reorganizations.
• chore: update tools.json #4692 — Both PRs swap AsyncAPI Generator ↔ AsyncAPI CLI names in config/all-tags.json and perform overlapping tool-entry renames/metadata swaps across tools.json variants.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

• derberg
• akshatnema
• anshgoyalevil
• sambhavgupta0705
• Mayaleeeee

Poem

🐰 A shuffle, a swap, a twist of the name—
Tags and tools dancing, none are the same!
Generator, CLI, SmartPaste take flight,
Golang joins the fold, the config feels right.
Our config now gleams with order anew! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'chore: update tools.json' is vague and generic. While it indicates a tools.json file was modified, it doesn't convey the substantial and complex nature of the changes, including the addition of a new Golang code generator, reordering of multiple tool entries, and numerous updates across different sections.	Consider a more descriptive title that captures the main change, such as 'chore: reorganize tools and add Golang AsyncAPI Code Generator' or 'chore: consolidate and update tools configuration.'

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-tools/regenerateTools

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (624747e) to head (13f2e68).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4754   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          798       798           
  Branches       146       146           
=========================================
  Hits           798       798           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🔴 Performance	37
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

Lighthouse ran on https://deploy-preview-4754--asyncapi-website.netlify.app/

[coderabbitai]

Actionable comments posted: 3

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (3)

config/all-tags.json (1)

280-319: Duplicate technology entries detected.

After the swap changes, there are now duplicate entries in the technologies array:

• Lines 311-314 and 315-319 both contain "SmartPaste" entries
• Lines 300-304 contain duplicate "VSCode" entries (both unchanged, but worth noting)

This duplication may cause issues with filtering or display logic. The technology tags should be unique.

🔎 Suggested fix: Remove duplicate entries

Consider deduplicating the technologies array. The second "SmartPaste" entry (lines 315-319) appears to be a duplicate that should be removed:

     {
       "name": "SmartPaste",
       "color": "bg-[#61d0f2]",
       "borderColor": "border-[#40ccf7]"
     },
-    {
-      "name": "SmartPaste",
-      "color": "bg-[#61d0f2]",
-      "borderColor": "border-[#40ccf7]"
-    },
     {
       "name": "IntelliJ IDEA",

config/tools.json (2)

2846-2924: Remove or document two unapproved HTML Template entries with null descriptions.

The entries for dipaksodani/async-gen and WSOL12/html-template lack descriptions and point to personal repositories, unlike the legitimate asyncapi/html-template entry at lines 2872–2897 which has proper documentation. These should be either removed from the tools list or provided with verified descriptions and justification for inclusion.

---

1375-1428: Remove duplicate AsyncAPI Studio entries with personal repository URLs.

The tools.json file contains two duplicate "AsyncAPI Studio" entries (lines 1375-1400 and 1402-1427) that point to personal GitHub repositories (TahaShahid203/async-api-issue and Shurtu-gal/action-test-bed) while using the official website URL (https://studio.asyncapi.com). These entries have null descriptions, unlike the legitimate entry (lines 1348-1374) which correctly references asyncapi/studio with an actual description. These duplicates should be removed as they create user confusion and indicate a data quality issue in the automated tool registration process.

♻️ Duplicate comments (3)

config/tools-automated.json (3)

368-405: Same AsyncAPI Studio data quality issue as in tools.json.

The entries at lines 373 and 392 point to personal/test repositories (TahaShahid203/async-api-issue and Shurtu-gal/action-test-bed) with null descriptions. This duplicates the issue identified in config/tools.json.

---

979-995: Personal fork HTML Template entries in Generator Templates section.

Same as in tools.json, entries for HTML Template point to personal forks:

• Lines 979-995: dipaksodani/async-gen with null description
• Lines 1074-1091: WSOL12/html-template with null description

These duplicate the official HTML Template entry and should be reviewed for removal.

Also applies to: 1074-1091

---

1116-1134: Duplicate AsyncAPI CLI entry in Others section.

Lines 1116-1134 contain another "AsyncAPI CLI" entry pointing to personal fork hkirat/asyncapi-fork. This is the same issue as in the CLIs section - personal forks should not be listed alongside official tools.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 624747e and 13f2e68.

📒 Files selected for processing (3)

• config/all-tags.json
• config/tools-automated.json
• config/tools.json

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2025-01-19T04:51:41.255Z

Learnt from: anshgoyalevil
Repo: asyncapi/website PR: 3557
File: tests/fixtures/markdown/check-edit-links-data.js:3-11
Timestamp: 2025-01-19T04:51:41.255Z
Learning: In the AsyncAPI website repository, the test data in `tests/fixtures/markdown/check-edit-links-data.js` intentionally includes inconsistent paths (with and without 'docs' prefix) to verify the script's ability to normalize and handle ambiguous path structures.

Applied to files:

• config/tools.json

📚 Learning: 2024-11-01T12:49:32.805Z

Learnt from: akshatnema
Repo: asyncapi/website PR: 3136
File: scripts/tools/combine-tools.js:122-125
Timestamp: 2024-11-01T12:49:32.805Z
Learning: In `scripts/tools/combine-tools.js`, the existing URL parsing logic for `repoUrl` without additional error handling is acceptable and does not require changes.

Applied to files:

• config/tools.json

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

• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Redirect rules - asyncapi-website
• GitHub Check: Header rules - asyncapi-website
• GitHub Check: Pages changed - asyncapi-website
• GitHub Check: Test NodeJS PR - windows-latest
• GitHub Check: Lighthouse CI
• GitHub Check: cypress-run

🔇 Additional comments (1)

config/tools-automated.json (1)

165-179: Entry is verified and legitimate.

The "Golang AsyncAPI Code Generator" entry points to an active repository that generates Go code from the broker to the application/user. The project has 111 stars and 27 forks, with recent activity as of March 2025. The tool can be installed via go install and supports the go generate workflow, confirming the entry's accuracy.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

GitHub Actions entries have inconsistent metadata after swap.

The GitHub Actions section shows swapped entries but with concerning inconsistencies:

1. "GitHub Action for CLI" (lines 516-530) points to asyncapi_github-action-for-generator repo but has isAsyncAPIOwner: false and describes it as for CLI
2. "GitHub Action for Generator" (lines 532-547) points to asyncapi/cli repo but has isAsyncAPIOwner: true and category github-actions (plural, inconsistent with github-action singular above)

The description for "GitHub Action for Generator" says "CLI to work with your AsyncAPI files" which doesn't match the title.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Duplicate AsyncAPI CLI entry pointing to personal fork.

Lines 830-848 contain an "AsyncAPI CLI" entry pointing to hkirat/asyncapi-fork - a personal fork with isAsyncAPIOwner: false. This duplicates the official AsyncAPI CLI entry (lines 762-779) that correctly points to asyncapi/cli.

Personal forks should not be listed alongside official tools unless they provide distinct functionality.

🤖 Prompt for AI Agents

config/tools-automated.json lines 830-848 contain a duplicate "AsyncAPI CLI"
entry pointing to a personal fork (hkirat/asyncapi-fork); remove this block (or
replace its repoUrl and websiteUrl to the official asyncapi/cli and set
isAsyncAPIOwner:true) so only the official AsyncAPI CLI entry remains; after the
change, validate the JSON and ensure no other personal fork entries duplicate
official tools.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Personal test repo listed as asyncapi-preview IDE extension.

The entry at lines 916-933 points to Savio629/testing2 for "asyncapi-preview" with isAsyncAPIOwner: false. This appears to be a test repository and should likely be removed.

🤖 Prompt for AI Agents

In config/tools-automated.json around lines 916-933, the listed
"asyncapi-preview" entry points to a personal test repo (Savio629/testing2) and
is marked isAsyncAPIOwner:false; remove this test entry from the JSON (delete
the entire object block for this extension), or if there is a legitimate public
extension to reference, replace the repoUrl with the correct upstream repo and
set isAsyncAPIOwner appropriately, then validate the JSON for syntax after the
change.