chore: update tools.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

Release Notes

• Chores
  • Updated AsyncAPI tools catalog with reorganized entries, renamed tools, and corrected metadata.
  • Added new tools to the catalog including Mokapi and asyncapi-python.
  • Corrected repository URLs and descriptions for several existing tools.
  • Updated language tag labels in the languages configuration.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	edfed29
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/69191ed90866a500082a4da9
😎 Deploy Preview	https://deploy-preview-4562--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 configuration files to swap language display names and reorganize tool catalog entries. Changes include renaming "SmartPaste" and "JetBrains" entries, restructuring tool metadata across code generators and GitHub Actions sections, and correcting language/category naming conventions.

Changes

Cohort / File(s)	Change Summary
Language tags config/all-tags.json	Display names swapped in languages array: "SmartPaste" renamed to "JetBrains" and vice versa
Automated tools catalog config/tools-automated.json	Tool entries reorganized and renamed across Code-first, Code Generators, Editors, and GitHub Actions sections; metadata updated (language casing, categories, URLs); items repositioned with owner/isAsyncAPIOwner flags adjusted
Tools catalog config/tools.json	GitHub Actions and CLI-related entries toggled: repoUrl values switched between official AsyncAPI CLI repo and fork; category values toggled between "github-action" and "github-actions"; descriptions nullified or restored

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

• Broad catalog reorganization: Multiple tool entries across distinct sections (Code Generators, GitHub Actions, Editors) require verification of correct classification, ownership flags, and URL assignments
• Interconnected changes: Tools catalog changes in all three JSON files appear coordinated; ensure swap consistency across all files
• Metadata validation: Language casing corrections, category naming, and URL field updates need cross-reference validation against actual project repositories
• Potential conflicts: High volume of related PRs with overlapping changes suggests risk of merge conflicts or duplicate edits; verify this PR's scope against concurrent modifications

Possibly related PRs

• chore: update tools.json #4270 — Same "SmartPaste"/"JetBrains" swap in all-tags.json with overlapping tools reorganizations
• chore: update tools.json #4332 — Overlapping data edits to config/tools-*.json files with similar tool entry reordering and metadata changes
• chore: update tools.json #4490 — Identical swaps and renames of language entries and tool metadata across the same configuration files

Suggested reviewers

• derberg
• akshatnema
• anshgoyalevil
• sambhavgupta0705
• Mayaleeeee

Poem

🐰 A rabbit hops through config land,
Where tags and tools now swap their brand,
SmartPaste meets JetBrains in the fray,
Tools reorganized every day,
Catalogs shuffle, metadata play!

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 overly vague and fails to convey the actual scope of changes across three configuration files and significant content reorganization.	Revise the title to reflect the actual changes, such as 'chore: reorganize tools and languages configuration' or 'chore: update tools, languages, and automated 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 (fe60602) to head (edfed29).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

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

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

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

[coderabbitai]

Actionable comments posted: 4

Caution

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

⚠️ Outside diff range comments (1)

config/tools-automated.json (1)

237-237: Correct language casing—use "Go/Golang" not "golang".

Line 237 uses lowercase "golang", but the language registry in all-tags.json defines the standard as "Go/Golang". Aligning this entry ensures consistent catalog filtering and display.

Apply this fix:

-          "language": "golang",
+          "language": "Go/Golang",

Also applies to: 237-237

📜 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 cecd342 and 8c4bb19.

📒 Files selected for processing (3)

• config/all-tags.json (1 hunks)
• config/tools-automated.json (20 hunks)
• config/tools.json (7 hunks)

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

• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Lighthouse CI

🔇 Additional comments (3)

config/all-tags.json (1)

286-286: LGTM—intentional display name swap consistent with catalog updates.

The swap between "JetBrains" and "SmartPaste" entries maintains proper structure and consistent metadata (color/borderColor pairs remain valid). Verified this aligns with the broader catalog reorganization noted in the PR objectives.

Also applies to: 291-291

config/tools-automated.json (1)

960-962: Language field must be a string, not an array.

Lines 960–962 and 981–983 in the AsyncAPI Generator Templates section define the language field as an array: "language": ["javascript"]. However, all other entries in the catalog use a string format: "language": "TypeScript". This structural inconsistency will cause downstream consumers (filters, display logic) to fail or behave unexpectedly when processing template entries.

Additionally, the value should be "JavaScript" (PascalCase) to match the language registry.

Apply these fixes:

     "filters": {
-      "language": ["javascript"],
+      "language": "JavaScript",
       "technology": [
         "HTML"
       ],

And similarly for line 981–983:

     "filters": {
-      "language": ["javascript"],
+      "language": "JavaScript",
       "technology": [
         "Spring Cloud Streams",

Also applies to: 981-983

⛔ Skipped due to learnings

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.

Learnt from: anshgoyalevil
Repo: asyncapi/website PR: 3950
File: scripts/utils/check-locales.ts:122-129
Timestamp: 2025-04-20T16:05:16.482Z
Learning: In the AsyncAPI website project, Next.js throws errors at runtime when locale files are missing, making additional validation for missing files unnecessary in the check-locales script.

Learnt from: akshatnema
Repo: asyncapi/website PR: 3423
File: tests/index.test.js:2-7
Timestamp: 2025-01-18T08:44:43.614Z
Learning: In the AsyncAPI website project, JavaScript test files must include the .ts extension when importing TypeScript files (e.g., `require('../scripts/build-rss.ts')`). This is a project-specific requirement enforced by the linting rules and build setup, even though it differs from typical Node.js behavior.

config/tools.json (1)

1754-1794: Consolidate duplicate "GitHub Action for Generator" entries and standardize category naming.

Verification confirms the identified issues:

• Duplicate entries confirmed: Both config/tools.json and config/tools-automated.json contain two "GitHub Action for Generator" entries with identical title but different repoUrls (asyncapi/cli vs actions-marketplace-validations/asyncapi_github-action-for-generator) and mismatched categories.
• Category inconsistency confirmed: Entry 1 uses "github-actions" (plural), Entry 2 uses "github-action" (singular). Across config/tools.json, only this single "github-actions" instance exists; the dominant form is "github-action" (singular).
• Systematic pattern confirmed: The identical duplication and category mismatch appear in both files, indicating a data consistency issue.

The different repoUrls suggest these entries may represent distinct tools (the CLI itself vs. a marketplace validation mirror), but their identical titles obscure this distinction.

Required actions:

1. Clarify whether both entries are necessary and document their semantic difference
2. Standardize categories to consistently use either "github-action" or "github-actions" across all GitHub Actions entries in both files
3. Update or consolidate entries accordingly

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Inconsistent language casing—use "TypeScript" not "Typescript".

Line 81 defines language as "Typescript" (mixed case), which is inconsistent with the standardized casing used throughout the catalog (e.g., "TypeScript" in all-tags.json and other entries). This may cause filtering or grouping logic to fail if consumers expect exact case matching.

Apply this fix:

-          "language": "Typescript",
+          "language": "TypeScript",

Also applies to: 81-81

🤖 Prompt for AI Agents

In config/tools-automated.json around line 81, the "language" field is set to
"Typescript" (incorrect casing); update the value to "TypeScript" to match the
catalog's standardized casing so consumers that perform exact string matching or
filtering behave consistently.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Standardize language casing—use "Python" not "python".

The asyncapi-python entry (line 219) defines language as lowercase "python", which is inconsistent with the language definitions in all-tags.json (which uses "Python"). Enforce consistent PascalCase casing across all language values to prevent filtering mismatches.

Apply this fix:

-          "language": "python",
+          "language": "Python",

Also applies to: 219-219

🤖 Prompt for AI Agents

In config/tools-automated.json around line 219 the "language" value is set to
lowercase "python", which is inconsistent with other entries that use PascalCase
"Python"; update this value to "Python" to standardize casing across the file
and avoid filtering mismatches.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Remove or consolidate duplicate "GitHub Action for Generator" entries with inconsistent metadata.

Lines 494–509 and 511–526 both define "GitHub Action for Generator" but with different repoUrls and category values:

• Entry 1 (line 494): repoUrl = asyncapi/cli, category = "github-actions" (plural)
• Entry 2 (line 511): repoUrl = asyncapi_github-action-for-generator, category = "github-action" (singular)

This duplication causes confusion about which is the authoritative repository and creates inconsistent category labeling. The PR summary mentions reorganization, but it's unclear whether both entries should coexist or if this is an unintended merge artifact.

Please clarify the intent:

1. Should only one canonical "GitHub Action for Generator" entry exist?
2. If both are valid, what distinguishes them (e.g., official vs community fork)?
3. Should the category be standardized to either "github-action" or "github-actions" across the catalog?

Once clarified, consolidate or remove the duplicate.

---

🏁 Script executed:

#!/bin/bash
# Examine the exact content around lines 494-526 in config/tools-automated.json
# Also check category consistency and find similar entries

echo "=== Content at lines 494-526 ==="
sed -n '494,526p' config/tools-automated.json

echo -e "\n=== Check for other entries with 'GitHub Action' in title ==="
rg -n '"title":\s*".*GitHub Action' config/tools-automated.json

echo -e "\n=== Find all unique category values to assess standardization ==="
rg -o '"categories":\s*\[\s*"[^"]+' config/tools-automated.json | sort | uniq -c | sort -rn

Length of output: 369

---

🏁 Script executed:

#!/bin/bash
# Examine the exact content around lines 494-526 in config/tools-automated.json
# Also check category consistency and find similar entries

echo "=== Content at lines 490-530 for full context ==="
sed -n '490,530p' config/tools-automated.json

echo -e "\n=== Check for all entries with 'GitHub Action' in title ==="
rg -n '"title":\s*".*GitHub Action' config/tools-automated.json -A 15

echo -e "\n=== Find all unique category values used in file ==="
rg -o '"categories":\s*\[\s*"[^"]+"' config/tools-automated.json | sort | uniq -c | sort -rn

Length of output: 2763

---

🏁 Script executed:

#!/bin/bash
# Check category consistency across entire file
# and understand the nature of the two entries

echo "=== All 'github-action' (singular) entries ==="
rg -n '"github-action"' config/tools-automated.json

echo -e "\n=== All 'github-actions' (plural) entries ==="
rg -n '"github-actions"' config/tools-automated.json

echo -e "\n=== Count unique category values ==="
rg -o '"categories":\s*\[\s*"[^"]+"' config/tools-automated.json | sed 's/.*"\([^"]*\)".*/\1/' | sort | uniq -c

Length of output: 196

---

🏁 Script executed:

#!/bin/bash
# Check if there's any PR metadata or context in common files
# that might explain these two entries

echo "=== Check for PR description or changelog references ==="
if [ -f "CHANGELOG.md" ]; then
  head -50 CHANGELOG.md
fi

echo -e "\n=== Look for any comments in the JSON about these entries ==="
sed -n '485,535p' config/tools-automated.json | grep -i "action\|marketplace"

echo -e "\n=== Check git history context (recent changes to this section) ==="
git log -1 --format="%B" -- config/tools-automated.json | head -20

Length of output: 598

---

Remove duplicate or clarify relationship between two "GitHub Action for Generator" entries; standardize categories.

The catalog contains two entries with identical titles but different repositories and inconsistent metadata:

• Entry 1 (lines 494–509): asyncapi/cli (official, isAsyncAPIOwner: true, has description, category: "github-actions")
• Entry 2 (lines 511–526): asyncapi_github-action-for-generator under actions-marketplace-validations/ (mirror validation, isAsyncAPIOwner: false, description is null, category: "github-action")

The second entry appears to be an automated marketplace validation mirror rather than a distinct tool. Keeping both entries with the same title creates ambiguity about which is authoritative. Additionally, "github-actions" and "github-action" are the only uses of these category values in the file—indicating an inconsistency.

Either remove the marketplace validation mirror entry or clearly document what distinguishes it from the official CLI entry and standardize the category naming.

🤖 Prompt for AI Agents

In config/tools-automated.json around lines 494 to 526 there are two entries
with the identical title "GitHub Action for Generator" that refer to different
repos and inconsistent metadata; remove or disambiguate the duplicate by either
deleting the marketplace validation mirror entry
(actions-marketplace-validations/asyncapi_github-action-for-generator) if it is
not a separate tool, or merge it into a single entry that clearly distinguishes
the mirror (e.g., add a note in description and set isAsyncAPIOwner correctly
for each), and while doing so standardize the category value to one canonical
form (change either "github-actions" or "github-action" to the chosen canonical
string across the file) so the catalog has a single authoritative entry and
consistent category naming.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Remove or consolidate duplicate AsyncAPI CLI entries with alternating repositories.

AsyncAPI CLI appears four times across the CLIs and Others sections (lines 2401–2422, 2424–2445, 3117–3138, 3140–3161) with identical descriptions but alternating between two repositories:

• Fork: https://github.com/hkirat/asyncapi-fork
• Official: https://github.com/asyncapi/cli

This duplication creates ambiguity about which repository is authoritative and results in consumers potentially loading the wrong version. The pattern suggests an incomplete merge or leftover test data. All entries should reference the single canonical repository: https://github.com/asyncapi/cli (the official AsyncAPI organization repo).

Apply this fix: Remove entries referencing the fork and retain only those pointing to https://github.com/asyncapi/cli. Example cleanup for the CLIs section:

         {
           "title": "AsyncAPI CLI",
           "description": "One CLI to rule them all...",
           "links": {
             "websiteUrl": "https://www.asyncapi.com/tools/cli",
-            "repoUrl": "https://github.com/hkirat/asyncapi-fork"
+            "repoUrl": "https://github.com/asyncapi/cli"
           },
           ...
         },
-        {
-          "title": "AsyncAPI CLI",
-          ...
-          "repoUrl": "https://github.com/asyncapi/cli"
-        },

Apply the same consolidation to the Others section.

Also applies to: 2428-2428, 3121-3121, 3144-3144

[princerajpoot20]

/rtm