[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fGs3y3a0yMvVk5xE8HW31LoslGuVA7u_JOZAnVtk4QJU":3},{"product":4,"cycleMajor":13,"releases":14,"cves":31,"nextMajor":9},{"id":5,"slug":6,"name":7,"category":8,"vendor":9,"description":10,"logo_url":9,"official_url":9,"synced_at":11,"created_at":12},"25f76196-6eec-4181-baa1-a4d511069f30","jruby","Jruby","other",null,"Developers working with Ruby on Java platforms rely on Jruby, a software solution that enables seamless integration of Ruby code with the Java Virtual Machine. Created to address the need for a compatible and efficient way to run Ruby applications on Java, Jruby has been maintained by a dedicated community since its inception. The ability to leverage Java's robust ecosystem while utilizing Ruby's dynamic programming capabilities has made Jruby a popular choice among developers, who appreciate the flexibility and performance it offers.\n\nThe Jruby landscape consists of 7 versions, with 4 of these versions having already reached their end-of-life. Currently, 3 active versions are available, with the latest stable version being 10.1.0.0. As developers plan their upgrades and maintenance schedules, it is essential to keep track of the end-of-life dates for each Jruby release. The next significant milestone is the end-of-life date for version 10.0, which is scheduled for 2028-04-01. This follows the last end-of-life date, which occurred on 2024-06-26 for version 9.3. Staying informed about these timelines allows developers to proactively manage their Jruby deployments and ensure uninterrupted support.\n\nGiven the current security landscape, Jruby has a clean slate with 0 tracked CVEs and 0 critical CVEs. As a result, there is no most affected version, and no Known Exploited Vulnerabilities (KEV) status applies. This positive security posture is a testament to the community's efforts in maintaining Jruby. Nevertheless, developers should remain vigilant and continue to monitor the security situation, taking proactive measures to upgrade to supported versions and apply necessary patches to minimize potential risks. By doing so, they can ensure the continued security and reliability of their Jruby applications.","2026-06-14T02:03:05.741+00:00","2026-05-30T16:23:55.904463+00:00","10",[15,23],{"id":16,"product_id":5,"cycle":17,"release_date":18,"eol":9,"eol_boolean":19,"latest":20,"latest_release_date":21,"lts":19,"support":9,"created_at":22},"641eedc6-4562-4b31-9dda-539953abd104","10.1","2026-04-21",false,"10.1.0.0","2026-04-20","2026-05-30T16:26:15.843031+00:00",{"id":24,"product_id":5,"cycle":25,"release_date":26,"eol":27,"eol_boolean":9,"latest":28,"latest_release_date":29,"lts":30,"support":9,"created_at":22},"a632ac9b-c7b2-48bf-953c-b93384c244ae","10.0","2025-04-14","2028-04-01","10.0.6.0","2026-06-11",true,[]]