ELISA adds 390-plus stress tests and token-level code history to Linux safety work
ELISA is bringing Cregit and stress-ng into its community as it works on shared tools and evidence for safety-critical Linux systems.
By RuntimeWire Staff · Published
Primary source: Linux Foundation Newsroom
Why it matters
Cregit and stress-ng add code-provenance and stress-testing tools to ELISA's safety work, while underscoring that tool access alone does not certify a Linux-based system.
On October 5th, the ELISA Fund added Cregit and stress-ng to its open-source community, bringing Linux code-history analysis and system stress testing into a project focused on safety-critical software. The announcement, published by the Linux Foundation, puts two established tools closer to ELISA's work on helping companies demonstrate that a specific Linux-based system meets safety requirements.
The move fits the project Kate Stewart helped launch in 2019: build shared methods and tools around Linux use in systems where software failure can cause serious harm. Stewart, the Linux Foundation's vice president of Dependable Embedded Systems, has spent more than 30 years in software and helped found SPDX, a standard for software license information. ELISA's approach is collaborative: its contributors work across engineering, safety and open-source communities rather than producing a separate Linux distribution.
That distinction shapes what the additions can do. Cregit traces the history of Linux kernel code at the level of individual tokens, helping developers inspect who introduced particular code and how it changed. Its co-creators include Daniel German, a University of Victoria computer science professor whose research covers open-source development and software evolution, and Bram Adams. Cregit's own project site explains that its views use an approach similar to Git blame, with the same kinds of attribution limitations.
stress-ng takes a different tack: it runs configurable workloads against a computer's subsystems and kernel interfaces to expose behavior under pressure. Its principal developer, Colin Ian King, describes the tool as having more than 390 stress tests. He also cautions that stress-ng is not intended to be a precise benchmark suite. ELISA's announcement describes it as a way to evaluate system behavior, reliability and performance; it does not say the project has certified the tool or made it part of a particular safety case.
Tools are ingredients, not certification
That qualification is central to understanding ELISA's role. The project says it does not produce a safe Linux distribution, engineer a customer's system to be safe, or remove a company's legal responsibilities. Instead, it provides a shared setting for defining tools, methods, processes and documentation that companies can use when preparing a specific system for certification. A tool's presence under the ELISA umbrella is not itself evidence that a product using it has passed a safety assessment. ELISA's FAQ sets out those limits.
The two additions address different points in that work. Cregit can help teams investigate code provenance and evolution; stress-ng can help them exercise system behavior under heavy loads. Together, they give maintainers and safety engineers more resources to consider. The announcement does not describe a combined workflow, changes to either tool, or a timetable for integrating them into ELISA guidance. The practical test will be whether developers can connect these tools to repeatable evidence and system-specific safety requirements.
ELISA Project Technical Steering Committee Chair Philipp Ahmann said bringing projects with different areas of focus into the same community could make it easier for developers to discover, use and contribute to open-source technologies that support safer and more reliable systems. The project is also convening work on requirements traceability, testing and documentation at the Safe Systems with Linux microconference in Prague, running October 5th-7th. ELISA is scheduled to appear at Open Source Summit Europe from October 7th-9th, where its safety-critical software track will include community contributors.
ELISA began in 2019 with founding corporate members Arm, BMW Car IT, KUKA, Linutronix and Toyota. Its job has remained focused on a hard gap in software development: Linux is widely adaptable, while safety certification requires a company to make a specific, documented case about how a particular system was built and tested. Cregit and stress-ng add useful technical capabilities to that effort. They do not make that case on their own.