chore: update tools.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

Changes

• Chores
  • Updated and reorganized tool registry entries across multiple categories with rebranding and reclassification.
  • Corrected tool metadata including names, descriptions, repository links, and category labels for improved accuracy.
  • Refreshed language entry configurations for consistency.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	898086b
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/68f584ee90558700086c02cb
😎 Deploy Preview	https://deploy-preview-4490--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

This PR swaps display names between "SmartPaste" and "JetBrains" in the language tags configuration, then performs extensive reorganization and reclassification of tools across the tools configuration files, including renaming entries, updating repository URLs, adjusting ownership and commercial flags, and correcting metadata categories.

Changes

Cohort / File(s)	Summary
Language Tags Configuration config/all-tags.json	Display names swapped between two language entries: "SmartPaste" ↔ "JetBrains"
Tools Automated Configuration config/tools-automated.json	Extensive tool reorganization across multiple sections: renamed entries (e.g., SIO-AsyncAPI → nestjs-asyncapi), reclassified tools between categories, updated repository/website URLs, toggled isAsyncAPIOwner and hasCommercial flags, introduced/removed null descriptions, and reassigned template entries with updated language and technology fields
Tools Configuration config/tools.json	Tool metadata updates: descriptions toggled between null and text values, repository URLs swapped across entries, category labels corrected (e.g., github-action → github-actions), and descriptive text adjusted for actions/generator templates

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

The changes span multiple configuration files with heterogeneous modifications—tool renames, section reassignments, flag toggling, and URL updates across tools-automated.json require careful verification of correctness. While changes are data-only (no logic), the scope and cross-section reorganization demand attention to ensure consistency and proper categorization.

Possibly related PRs

• chore: update tools.json #4467: Performs the exact same "JetBrains" ↔ "SmartPaste" name swap in config/all-tags.json.
• chore: update tools.json #4230: Applies matching JSON metadata edits with identical tool reorganization patterns across config files.
• chore: update tools.json #4459: Contains overlapping metadata swaps and extensive tool renames/reclassifications in tools configuration files.

Suggested reviewers

• derberg
• akshatnema
• anshgoyalevil
• sambhavgupta0705

Poem

🐰 A shuffle here, a swap of names,
SmartPaste and JetBrains trade their frames,
Tools reorganized with care and grace,
Each config finds its rightful place! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The pull request title "chore: update tools.json" is misleading because it references only one file when the changeset actually modifies three files: config/all-tags.json, config/tools-automated.json, and config/tools.json. The most significant changes (rated as "High" code review effort) occur in config/tools-automated.json, which involves extensive tool rebranding, reclassification, and reorganization across multiple sections. The title completely omits these substantial changes and suggests the PR only updates tools.json, which would give reviewers and team members scanning the history an inaccurate understanding of the scope and impact of the changes.	Update the title to more accurately reflect the full scope of changes across all three modified files. A more descriptive title such as "chore: regenerate and update tool configurations" or "chore: update tools and language configurations" would better represent the multi-file nature and the extensive reorganization of tool metadata throughout the changeset.

✅ 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 changes. Docstring coverage check skipped.

✨ 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 (db754f6) to head (898086b).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

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

☔ 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-4490--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 (5)

config/tools.json (2)

1308-1388: Multiple AsyncAPI Studio entries with inconsistent repository URLs.

The file contains three separate AsyncAPI Studio entries (lines 1308, 1335, 1362) with different configurations:

• Line 1313: https://github.com/Shurtu-gal/action-test-bed (appears to be a test repo)
• Line 1340: https://github.com/TahaShahid203/async-api-issue (appears to be a test/issue repo)
• Line 1367: https://github.com/asyncapi/studio (official repo)

Only one canonical entry should exist unless multiple independent implementations are intentional. Verify that non-official repositories should be included in the production configuration.

---

2450-2450: Update repoUrl to point to the correct AsyncAPI-format repository.

Line 2450 should reference https://github.com/thim81/asyncapi-format (the JavaScript AsyncAPI formatter), not https://github.com/asyncapi/converter-go (the Go version converter tool). These are different tools with different purposes.

          "repoUrl": "https://github.com/thim81/asyncapi-format"

config/tools-automated.json (3)

328-382: Multiple AsyncAPI Studio entries with inconsistent metadata.

Three AsyncAPI Studio entries exist in the Editors section with variations:

• Line 328: description: null, repoUrl: "https://github.com/Shurtu-gal/action-test-bed", isAsyncAPIOwner: false
• Line 348: description: null, repoUrl: "https://github.com/TahaShahid203/async-api-issue", isAsyncAPIOwner: false
• Line 366: description: "Visually design...", repoUrl: "https://github.com/asyncapi/studio", isAsyncAPIOwner: true

Only the third entry has a description and points to the official AsyncAPI repository. Remove duplicate entries with test/fork repositories and null descriptions, retaining only the canonical official entry.

---

719-755: Duplicate AsyncAPI CLI entries with conflicting ownership and repository URLs.

Two AsyncAPI CLI entries in the CLIs section:

• Line 719-735: repoUrl: "https://github.com/hkirat/asyncapi-fork", isAsyncAPIOwner: false
• Line 738-754: repoUrl: "https://github.com/asyncapi/cli", isAsyncAPIOwner: true

Only one entry should exist, referencing the official AsyncAPI repository. Consolidate to a single canonical entry and remove the fork reference.

---

918-1031: Language field inconsistency in AsyncAPI Generator Templates.

Several generator template entries use "language": "javascript" (string, line 967) while others use "language": ["javascript"] (array, lines 925, 946, 985, 1003). This inconsistency in data structure may cause parsing or filtering issues in downstream systems. Standardize all language fields to use the same format (either all strings or all arrays).

📜 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 841a1d3 and 898086b.

📒 Files selected for processing (3)

• config/all-tags.json (1 hunks)
• config/tools-automated.json (26 hunks)
• config/tools.json (9 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). (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 (3)

config/all-tags.json (1)

281-281: Tag names swapped — verify semantic correctness.

Lines 281 and 286 swap the names "JetBrains" and "SmartPaste" in the technologies array. Confirm that these names are semantically associated with the correct entries (color codes and the context in which they are used across the tool registry).

Also applies to: 286-286

config/tools-automated.json (2)

53-92: Potential duplicate tools: nestjs-asyncapi vs SIO-AsyncAPI reorganization.

The file reorganizes tools in the Code-first tools section:

• Line 53: Entry renamed to nestjs-asyncapi with TypeScript/Node.js/NestJS stack
• Line 72: A separate SIO-AsyncAPI entry with Python/Socket.IO/Flask stack

This appears to be a rename/swap of two distinct tools rather than duplication. However, verify the intent: should these represent two separate tools or is one replacing the other? The naming suggests nestjs-asyncapi is the original "SIO-AsyncAPI" renamed, but the presence of both entries creates ambiguity.

---

779-800: New entry: Specmatic added to CLIs section with duplicate in Mocking and Testing.

Line 779-800 adds a Specmatic entry to the CLIs section. However, Specmatic is already listed in the "Mocking and Testing" section (line 555-576) with identical metadata. Verify if this is intentional cross-categorization or accidental duplication. If intentional, ensure the data remains synchronized across sections.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

AsyncAPI CLI fork repository appears twice in Others section.

The Others section contains two AsyncAPI CLI entries with different repositories:

• Line 1062: https://github.com/hkirat/asyncapi-fork
• Line 1081: https://github.com/asyncapi/cli

Same consolidation issue as in the CLIs section. Remove the fork reference and retain only the official repository.

Also applies to: 1081-1081

🤖 Prompt for AI Agents

In config/tools-automated.json around lines 1062 to 1062, the "Others" section
contains a duplicate AsyncAPI CLI entry pointing to the fork repository
(https://github.com/hkirat/asyncapi-fork); remove that fork entry so only the
official AsyncAPI CLI repository (https://github.com/asyncapi/cli) remains (also
verify and remove any other duplicate fork entries such as at line 1081 if
present), ensuring the JSON stays valid after deletion.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Inconsistent category naming: github-action vs github-actions.

Two "GitHub Action for Generator" entries use different category values:

• Line 1769: "github-actions" (plural)
• Line 1790: "github-action" (singular)

Additionally, the entries point to different repositories (line 1757 vs 1778), and descriptions differ (line 1755 vs line 1776 is null). Establish a consistent category naming convention and verify both tool variants are necessary.

Also applies to: 1757-1757, 1769-1769, 1776-1776, 1778-1778, 1790-1790

🤖 Prompt for AI Agents

In config/tools.json around lines 1755-1790, there are inconsistent entries for
the "GitHub Action for Generator" — category uses both "github-action" and
"github-actions", the two entries point to different repositories, and one
description is null; unify the category to a single convention (use
"github-actions"), verify whether both repository entries are required and if
not consolidate into one canonical entry, copy a non-null description into the
remaining entry (or provide a short descriptive sentence if both are necessary),
and ensure both entries (if kept) have consistent fields (category, repository
URL, and description) to avoid duplication.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

AsyncAPI CLI repository URL inconsistency across duplicate entries.

Two AsyncAPI CLI entries in the CLIs section reference different repositories:

• Line 2405: https://github.com/hkirat/asyncapi-fork (fork)
• Line 2428: https://github.com/asyncapi/cli (official)

Duplicate tool entries with conflicting metadata suggest a data consolidation issue. Retain only the official repository entry and remove duplicates.

Also applies to: 2428-2428

🤖 Prompt for AI Agents

In config/tools.json around lines 2405 and 2428, there are duplicate AsyncAPI
CLI entries with conflicting repoUrl values; remove the duplicate that points to
the fork (https://github.com/hkirat/asyncapi-fork at ~line 2405) and keep only
the official entry (https://github.com/asyncapi/cli at ~line 2428), ensuring the
CLIs array contains a single AsyncAPI CLI object with the official repoUrl and
that any related fields (name, id, etc.) are consistent.