chore: update tools.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Updated tool catalog metadata including descriptions, repository links, and ownership/licensing attributes
  • Reorganized tools across categories and added new "Code-first tools" section
  • Corrected category identifiers and language/technology tags
  • Refreshed repository references for accuracy

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	f4b77d9
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/6907fa0818ce1a00084f85f9
😎 Deploy Preview	https://deploy-preview-4525--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

The PR updates three configuration files: swapping language and technology entries in all-tags.json, reorganizing the tools catalog in tools-automated.json with new sections and metadata changes, and updating descriptions and repository URLs in tools.json.

Changes

Cohort / File(s)	Summary
Tag Configuration config/all-tags.json	Swapped adjacent language entries: "TypeScript" ↔ "Socket.IO"; swapped adjacent technology entries: "JetBrains" ↔ "SmartPaste"
Automated Tools Catalog Reorganization config/tools-automated.json	Removed AsyncAPI Server API from APIs section; added new "Code-first tools" section; reorganized multiple sections (Code Generators, Validators, GitHub Actions, Editors, Frameworks, Templates, etc.); updated titles, descriptions, repository links, ownership flags, commercial flags, and category identifiers across numerous tool entries
Tools Metadata Updates config/tools.json	Swapped description values (null ↔ text) for multiple entries; updated repository URLs; corrected category identifiers ("github-action" vs "github-actions")

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~75 minutes

• tools-automated.json requires careful verification: new "Code-first tools" section, extensive tool relocations across multiple categories, and numerous metadata field changes (ownership/commercial flags, descriptions, URLs) affecting public-facing tool listings
• Verify all repository links and documentation URLs are correctly swapped or updated
• Confirm category identifier corrections align with expected taxonomy
• Cross-reference moved/duplicated tool entries to ensure no unintended duplications or missing entries, particularly in Generator/Template sections
• Review ownership flag changes (isAsyncAPIOwner) to ensure appropriate tool attribution

Possibly related PRs

• chore: update tools.json #4203: Modifies the same JSON configuration files with similar entry renames, reorders, and metadata swaps (descriptions, URLs, categories)
• chore: update tools.json #4354: Updates the same config files including identical TypeScript/Socket.IO swaps in all-tags.json and matching tools reorganization
• chore: update tools.json #4332: Overlapping edits to tools-automated.json and tools.json with same tool reclassifications (GitHub Actions, Mokapi/Specmatic, generator templates, code-first tools)

Suggested reviewers

• derberg
• akshatnema
• anshgoyalevil
• sambhavgupta0705
• Mayaleeeee
• devilkiller-ag
• vishvamsinh28

Poem

🐰 Tags and tools dance in JSON delight,
Swapping their places left and right,
SmartPaste and JetBrains twirl and trade,
New sections bloom as old ones fade,
A catalog refreshed, reorganized and bright! ✨

Pre-merge checks and finishing touches

✅ 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 "chore: update tools.json" is partially related to the changeset. While it accurately describes changes made to config/tools.json, the changeset actually modifies three files: config/all-tags.json, config/tools-automated.json, and config/tools.json. The title omits two other modified files and does not capture the most significant changes, which are the extensive reorganization and metadata updates in config/tools-automated.json (marked as "High" code review effort). The title refers to a real part of the change but not the main point or full scope of the changeset.

✨ 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 (053e5a6) to head (f4b77d9).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4525   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          780       780           
  Branches       144       144           
=========================================
  Hits           780       780           

☔ 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	41
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

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

[coderabbitai]

Actionable comments posted: 1

Caution

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

⚠️ Outside diff range comments (2)

config/tools-automated.json (2)

6-25: Remove duplicate tool entries: 11+ tools appear with identical metadata across multiple sections.

Verification confirms this is systemic, not isolated to SIO-AsyncAPI. These tools have exact duplicate entries with identical metadata:

• SIO-AsyncAPI (lines 6 & 138)
• AsyncAPI CLI (multiple entries)
• GitHub Action for Generator (multiple entries)
• Mokapi, Specmatic, ZenWave SDK, Zod Sockets, asyncapi-preview, HTML Template, AsyncAPI Studio, and others

Since entries are word-for-word identical across sections, consolidate by either:

1. Keeping the entry in only one appropriate section
2. Or moving duplicates to a single canonical location

Identical metadata indicates these are unintentional duplicates from generation or merge conflict, not intentional re-categorization.

---

741-826: Consolidate four duplicate AsyncAPI CLI entries across sections.

The file contains four "AsyncAPI CLI" entries—not three as initially noted—distributed across CLIs and Others sections:

• CLIs section (lines 741–757): Official repo (asyncapi/cli), isAsyncAPIOwner: true
• CLIs section (lines 809–826): Fork repo (hkirat/asyncapi-fork), isAsyncAPIOwner: false
• Others section (lines 1058–1075): Official repo (asyncapi/cli), isAsyncAPIOwner: true
• Others section (lines 1077–1095): Fork repo (hkirat/asyncapi-fork), isAsyncAPIOwner: false

Remove redundant entries or clearly distinguish them in titles/descriptions. The fork entry should not appear in multiple sections unchanged.

🧹 Nitpick comments (1)

config/tools-automated.json (1)

918-1051: Template section reorganization with mixed language field formats and null descriptions.

The "AsyncAPI Generator Templates" section has been reorganized with:

• Language field as both string (line 966: "language": "javascript") and array (lines 924–926, 946–948, 1002–1004).
• Some entries with "description": null (line 1018) while similar entries have descriptions (line 979).

Per retrieved learnings, both string and array formats for language are acceptable. However, ensure:

• Consistency in how the consuming code handles both formats.
• Null descriptions are intentional or should be populated with meaningful text.

📜 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 053e5a6 and f4b77d9.

📒 Files selected for processing (3)

• config/all-tags.json (3 hunks)
• config/tools-automated.json (25 hunks)
• config/tools.json (11 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2024-11-01T12:48:22.034Z

Learnt from: akshatnema
Repo: asyncapi/website PR: 3136
File: tests/fixtures/tools/automated-tools.json:8-9
Timestamp: 2024-11-01T12:48:22.034Z
Learning: In the `tests/fixtures/tools/automated-tools.json` file, the `language` field within the `filters` object can be either a string or an array. Both formats are acceptable and supported in the codebase.

Applied to files:

• config/tools-automated.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). (6)

• 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

🔇 Additional comments (9)

config/all-tags.json (1)

181-189: Tag order changes require verification of cascading impacts.

The swaps of "Socket.IO"/"TypeScript" (lines 181–189) and "SmartPaste"/"JetBrains" (lines 281–294) in the technologies section are metadata-only updates. Verify that:

• These tag names are used consistently in config/tools.json and config/tools-automated.json where tools reference them.
• Any client-side code that depends on tag order (e.g., UI rendering, filtering) handles the reordering correctly.

Also applies to: 281-294

config/tools.json (4)

1755-1770: Inconsistent category naming for GitHub Actions: "github-action" vs "github-actions".

Line 1769 uses "github-action" while line 1790 uses "github-actions" (plural). Verify that:

• This difference is intentional or reflects a schema change.
• All category references across the codebase consistently use the same identifier.
• Client-side filtering/grouping code handles both forms if intentional, or normalize to a single form.

Also applies to: 1775-1794

---

1309-1368: Multiple "AsyncAPI Studio" entries with different descriptions, URLs, and ownership.

Three separate "AsyncAPI Studio" entries appear with conflicting metadata:

• Line 1310–1313: Official studio with detailed description and asyncapi/studio repo.
• Line 1337–1340: Same title, description: null, and TahaShahid203/async-api-issue fork.
• Line 1363–1367: Same title, description: null, and Shurtu-gal/action-test-bed fork.

Clarify whether this duplication is intentional (e.g., documenting alternative forks) or a data quality issue. If intentional, consider adding a distinguishing identifier or description to clarify the purpose of each entry.

---

2401-2445: Multiple "AsyncAPI CLI" entries with different repository URLs.

Two separate entries reference the same tool but point to different repositories:

• Line 2405: Official repository (asyncapi/cli).
• Line 2428: Fork (hkirat/asyncapi-fork).

Verify whether both should be listed as separate tools or if this is unintended duplication. If both are intentional (e.g., documenting forks), ensure descriptions distinguish them clearly.

---

2657-2711: Multiple "asyncapi-preview" entries with different repository URLs.

Two entries for the same VSCode extension with different repositories:

• Line 2664: Official repository (asyncapi/vs-asyncapi-preview).
• Line 2690: Alternate repository (Savio629/testing2).

Confirm whether both repositories should be listed. If documenting variants, ensure clarity in descriptions or metadata to distinguish them.

config/tools-automated.json (4)

856-911: Multiple asyncapi-preview VSCode extension entries with inconsistent ownership.

Two "asyncapi-preview" entries with different repositories and ownership flags:

• Lines 856–871: Official repo (asyncapi/vs-asyncapi-preview), isAsyncAPIOwner: true
• Lines 874–889: Alternate repo (Savio629/testing2), isAsyncAPIOwner: false

Clarify whether both should be listed separately or consolidated. If both are intentional, add descriptions to distinguish their purpose (e.g., "official" vs "community fork").

---

532-602: Specmatic and Mokapi listed in multiple sections with potential duplication.

Both "Specmatic" (lines 533–552) and "Mokapi" (lines 581–601) appear in the "Mocking and Testing" section and are also listed in the "CLIs" section later (lines 719–738 for Specmatic, lines 786–806 for Mokapi).

Verify whether:

• This duplication is intentional because the tools serve multiple purposes.
• One set of entries should be removed to reduce redundancy.
• If intentional, ensure descriptions or metadata differ to justify separate listings.

---

652-669: New "AsyncAPI Validation" entry added to Validators section.

A new tool "AsyncAPI Validation" has been added at lines 652–669. Verify:

• Whether this is a new tool or a relocated/renamed entry from another section.
• That the metadata (language, technology, etc.) is accurate and complete.
• Whether it should also appear in other related sections (e.g., "Code Generators" or "Compare tools").

---

298-298: Empty "Directories" section.

The "Directories" section (line 298) has an empty toolsList: []. Verify whether:

• This is intentional (e.g., pending tool additions).
• Tools should be migrated into this section from other sections.
• This section should be removed if permanently empty.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Inconsistent ownership flag for GitHub Action for Generator entries.

Two "GitHub Action for Generator" entries have conflicting isAsyncAPIOwner values:

• Line 507: "isAsyncAPIOwner": false with repo actions-marketplace-validations/asyncapi_github-action-for-generator
• Line 524: "isAsyncAPIOwner": true with repo asyncapi/cli and description mentioning CLI functionality

The first entry has description: null while the second has a detailed description. Clarify whether these are:

• Distinct tools that should be renamed to avoid confusion.
• Different versions/providers of the same tool, with only one being official.
• Data quality issues from the automated generation process.

---

---

🏁 Script executed:

```shell
#!/bin/bash
# Inspect the full entries and surrounding context in tools-automated.json
cat config/tools-automated.json | jq '.[] | select(.title == "GitHub Action for Generator")'

Length of output: 0

---

🏁 Script executed:

#!/bin/bash
# Search for all entries with "GitHub Action" in title to identify patterns
cat config/tools-automated.json | jq '.[] | select(.title | contains("GitHub Action")) | {title, description: (.description | if . then (. | length) else "null" end), repoUrl: .links.repoUrl, isAsyncAPIOwner}'

Length of output: 106

---

🏁 Script executed:

#!/bin/bash
# Get context around line 494-526 to see surrounding entries
sed -n '450,550p' config/tools-automated.json

Length of output: 3297

---

---

🌐 Web query:

```web
asyncapi cli repository GitHub tool purpose

💡 Result:

The asyncapi/cli GitHub repository is the official CLI tool for working with AsyncAPI documents — used to create/boot‑strap specs, validate and convert AsyncAPI files, generate docs/code (via Generator/Modelina), optimize/bundle specs, compare differences, and start the AsyncAPI Studio locally. It's built with oclif, published as @asyncapi/cli, and also exposed as a GitHub Action for CI use. [1][2][3]

Sources:

• GitHub repo (README & code). [1]
• AsyncAPI docs (CLI features & architecture). [2]
• AsyncAPI tools page (installer, examples, GitHub Action). [3]

---

🌐 Web query:

asyncapi github action generator actions-marketplace-validations

💡 Result:

Short answer: AsyncAPI provides official GitHub Actions for validation and generation (the validator action by Waleed Ashraf and the AsyncAPI generator/CLI actions). The "actions-marketplace-validations" namespace you’re seeing is a separate GitHub Actions namespace (not the AsyncAPI project) that hosts many third-party/automatically-created action repos used for Marketplace/validation purposes. If you want the AsyncAPI generator action use asyncapi/github-action-for-generator or asyncapi/cli (both documented by AsyncAPI). [1][2][3]

Sources:

• AsyncAPI blog post mentioning the validator and generator actions. [1]
• AsyncAPI docs: GitHub Action for CLI (generator/validate usage). [2]
• AsyncAPI tools / GitHub Actions overview. [3]

---

Clarify misleading titles and descriptions for GitHub Actions entries.

While the isAsyncAPIOwner flags are correct (the actions-marketplace-validations repo is third-party), the two entries have identical titles despite being different tools:

• Entry 1 (actions-marketplace-validations/asyncapi_github-action-for-generator): A third-party marketplace validation mirror with description: null
• Entry 2 (asyncapi/cli): The official AsyncAPI CLI, which also functions as a GitHub Action, but is described as a CLI tool

Rename entries to avoid confusion:

• Entry 1: Add a descriptive title (e.g., "Marketplace Validation Mirror") and description, or remove if redundant
• Entry 2: Rename to "AsyncAPI CLI" or "GitHub Action for AsyncAPI CLI" to clarify it's a CLI that also works as an action, not solely a GitHub Action for code generation
• Standardize category naming (github-action vs github-actions)

🤖 Prompt for AI Agents

In config/tools-automated.json around lines 494 to 526, the two adjacent GitHub
Action entries have identical titles and inconsistent category naming which is
misleading; update the first entry
(actions-marketplace-validations/asyncapi_github-action-for-generator) to a
distinct title such as "Marketplace Validation Mirror" and add a short
description like "Mirror of marketplace validation for the AsyncAPI Generator
GitHub Action" (keep isAsyncAPIOwner false), update the second entry's title to
"AsyncAPI CLI" (or "GitHub Action for AsyncAPI CLI") and ensure its description
reflects that it is the official CLI which can be used as a GitHub Action (keep
isAsyncAPIOwner true), and standardize the category field on both entries to use
the same value (change "github-actions" to "github-action" or vice versa) for
consistency.