[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fXxRaL_hxyLe0O5RXXHuGzoNYjACL0WNU6SqKOQz41QI":3},{"product":4,"cycleMajor":13,"releases":14,"cves":57,"nextMajor":58},{"id":5,"slug":6,"name":7,"category":8,"vendor":9,"description":10,"logo_url":9,"official_url":9,"synced_at":11,"created_at":12},"4f38983c-bf03-4597-9f6c-fa97ab38080b","emberjs","Emberjs","other",null,"Developers rely on Emberjs to build ambitious web applications, and for good reason - since its creation, the framework has been maintained by a dedicated community that ensures its stability and security. The first version of Emberjs was released in 2011, and over the years, it has undergone significant transformations to become the robust tool it is today. With a large number of versions, tracking the end-of-life dates of each release is crucial for developers to plan their upgrades and ensure the security of their applications. Emberjs has been widely adopted due to its ability to handle complex, data-driven interfaces, making it a popular choice among developers.\n\nThe end-of-life landscape for Emberjs is complex, with a total of 42 versions, out of which 38 have already reached their end-of-life. Currently, only 4 versions are still supported, with the latest stable version being 6.12.0. Developers should be aware that version 6.4 is next in line to expire, with its end-of-life date set for 2026-06-22. This means that any applications still running on version 6.4 will no longer receive security patches or updates after this date. The most recent version to reach end-of-life was 6.11, which expired on 2026-05-01. With such a large number of versions already expired, it is essential for developers to stay on top of the end-of-life dates to avoid any potential security risks.\n\nGiven the current security landscape, Emberjs has a clean track record, with no known CVEs, including no critical ones. As a result, there is no most affected version, and no action is required in terms of patching or upgrading to address any known security vulnerabilities. However, this does not mean that developers can be complacent - it is still crucial to keep their applications up-to-date with the latest versions of Emberjs to ensure they receive any future security patches or updates. By tracking the end-of-life dates and staying informed about the latest developments, developers can ensure the security and stability of their applications, and take advantage of the latest features and improvements that Emberjs has to offer.","2026-08-12T02:02:02.024+00:00","2026-05-30T16:23:55.845073+00:00","2",[15,25,33,41,49],{"id":16,"product_id":5,"cycle":17,"release_date":18,"eol":19,"eol_boolean":9,"latest":20,"latest_release_date":21,"lts":22,"support":23,"created_at":24},"67322d3d-3593-4930-8901-8ac2d59b1eed","2.18","2018-01-01","2019-02-27","2.18.3","2026-01-30",true,"2018-09-12","2026-05-30T16:35:24.470185+00:00",{"id":26,"product_id":5,"cycle":27,"release_date":28,"eol":29,"eol_boolean":9,"latest":30,"latest_release_date":31,"lts":22,"support":32,"created_at":24},"844c7de2-aa24-424d-aba6-7c77bf52b176","2.16","2017-10-10","2018-12-03","2.16.4","2018-02-14","2018-06-18",{"id":34,"product_id":5,"cycle":35,"release_date":36,"eol":37,"eol_boolean":9,"latest":38,"latest_release_date":39,"lts":22,"support":40,"created_at":24},"0c6f6c19-fb50-452d-8881-f83fbf91bbd7","2.12","2017-03-15","2018-05-12","2.12.2","2017-04-27","2017-11-25",{"id":42,"product_id":5,"cycle":43,"release_date":44,"eol":45,"eol_boolean":9,"latest":46,"latest_release_date":47,"lts":22,"support":48,"created_at":24},"8332cd0e-897e-4f0c-81cc-6cfa25d130d8","2.8","2016-09-09","2017-10-30","2.8.3","2016-11-01","2017-05-15",{"id":50,"product_id":5,"cycle":51,"release_date":52,"eol":53,"eol_boolean":9,"latest":54,"latest_release_date":55,"lts":22,"support":56,"created_at":24},"35654b27-ab2e-4ceb-8f51-bbbbbfe147bf","2.4","2016-02-29","2017-04-24","2.4.6","2016-06-05","2016-11-07",[],"3"]