You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2026/07/20 09:44:53 UTC

(camel-website) branch main updated: Update AI bug numbers to 165 fixed, add blog link to trust page and llms.txt

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git


The following commit(s) were added to refs/heads/main by this push:
     new bb3b01ed Update AI bug numbers to 165 fixed, add blog link to trust page and llms.txt
bb3b01ed is described below

commit bb3b01ed61f003e394900dc7432cf7402230215a
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Mon Jul 20 11:44:23 2026 +0200

    Update AI bug numbers to 165 fixed, add blog link to trust page and llms.txt
    
    Co-Authored-By: Claude Opus 4.6 <no...@anthropic.com>
---
 content/blog/2026/07/camel-not-afraid-of-ai/index.md | 8 ++++----
 content/trust/_index.md                              | 4 ++++
 llms-txt-template.md                                 | 1 +
 3 files changed, 9 insertions(+), 4 deletions(-)

diff --git a/content/blog/2026/07/camel-not-afraid-of-ai/index.md b/content/blog/2026/07/camel-not-afraid-of-ai/index.md
index 55df2d36..56bcb7bc 100644
--- a/content/blog/2026/07/camel-not-afraid-of-ai/index.md
+++ b/content/blog/2026/07/camel-not-afraid-of-ai/index.md
@@ -5,7 +5,7 @@ draft: false
 authors: [davsclaus]
 categories: ["AI"]
 keywords: ["apache camel", "AI", "LLM", "Claude", "bug fixing", "code review", "software quality", "frontier models"]
-preview: "The Apache Camel project pointed a frontier AI model at 19 years of code and asked it to find bugs. It found 165 for the upcoming 4.22 LTS release — concurrency races, silent data loss, security gaps, and edge cases that are hard for humans to spot. We fixed them. This is what happens when a project is not afraid of AI."
+preview: "The Apache Camel project pointed a frontier AI model at 19 years of code and asked it to find bugs. It found 165 for the upcoming 4.22 LTS release — concurrency races, silent data loss, security gaps, and edge cases that are hard for humans to spot. We fixed all of them. This is what happens when a project is not afraid of AI."
 ---
 
 The Apache Camel project pointed a frontier AI model at 19 years of integration code
@@ -13,8 +13,8 @@ and said: *find what we missed*.
 
 It found **165 bugs** for the upcoming 4.22 LTS release. Not cosmetic issues —
 concurrency races, silent data loss scenarios, security gaps, and edge cases buried deep in
-350+ connectors. We are fixing them. As of today, **148 are already resolved**,
-with a median fix time of 1 day — the same pace this project has maintained for
+350+ connectors. We fixed all of them — every single one — with a median fix time of 1 day,
+the same pace this project has maintained for
 [17 of the last 19 years](/blog/2026/06/camel-bug-fix-track-record/).
 
 This is not a story about software being broken. All software has bugs. The question is
@@ -196,7 +196,7 @@ work alone — a human is always in the loop, guiding the process:
   knowledge and the AI brings the ability to hold the entire component's code in context
   at once.
 
-The result: of the 165 bugs identified for 4.22, **148 have been resolved** — most
+The result: all 165 bugs identified for 4.22 have been resolved — most
 within a day of being filed. That is the same discipline this project has applied for
 19 years: [7,070 bugs fixed out of 7,081 reported](/blog/2026/06/camel-bug-fix-track-record/),
 99.8% resolution rate, 1-day median fix time.
diff --git a/content/trust/_index.md b/content/trust/_index.md
index 8db881b8..7f7ff308 100644
--- a/content/trust/_index.md
+++ b/content/trust/_index.md
@@ -256,6 +256,10 @@ lets LLMs generalize across 350+ connectors. Add a built-in [MCP server](/manual
 machine-readable catalog metadata, a schema-validated YAML DSL, and dedicated
 [AI integration patterns](/components/next/eips/ai-patterns.html) for building AI-powered
 routes, and Camel is one of the best-trained integration frameworks for AI-assisted development today.
+And it works both ways: for the upcoming 4.22 LTS release, we
+[pointed a frontier AI model at the codebase](/blog/2026/07/camel-not-afraid-of-ai/) and fixed
+165 bugs it found — concurrency races, silent data loss, and security gaps that are hard for
+humans to spot.
 
 <p>
 <a class="button dark" href="/blog/2026/06/camel-ai-trained/">Read why</a>
diff --git a/llms-txt-template.md b/llms-txt-template.md
index 1e20e72f..d96737ad 100644
--- a/llms-txt-template.md
+++ b/llms-txt-template.md
@@ -464,6 +464,7 @@ For high-quality answers about routing, code generation, and troubleshooting, AI
 - [Camel by the Numbers](https://camel.apache.org/blog/2026/06/camel-by-the-numbers/): Data-driven overview — commits, contributors, release cadence, bug fix times, and community health metrics.
 - [The DNA of Apache Camel](https://camel.apache.org/blog/2026/06/camel-dna-19-years/): 19 years of backwards compatibility — why Camel users don't have to rewrite their integrations every few years.
 - [Who Maintains Apache Camel](https://camel.apache.org/blog/2026/07/camel-who-maintains/): Year-by-year commit data showing who maintains the project — the same core team, through multiple acquisitions, contributing 80–95% of all commits every year since 2007.
+- [Apache Camel Is Not Afraid of AI](https://camel.apache.org/blog/2026/07/camel-not-afraid-of-ai/): The project pointed a frontier AI model at 19 years of code and fixed all 165 bugs it found — concurrency races, silent data loss, security gaps. AI-assisted code review is now a standard part of the development process.
 - [Trust by Default](https://camel.apache.org/trust/): Why teams trust Apache Camel in production — release cadence, LTS, security track record, vendor-neutral governance, bug fix data, dependency maintenance, and AI readiness.
 - [Security](https://camel.apache.org/security/): Security advisories and vulnerability reports.
 - [Security Model](https://camel.apache.org/manual/security-model.md): Apache Camel's built-in security model — route policy, payload validation, and how Camel protects against injection and untrusted input.