LOBSTER
The Lightweight Open BMW Software Traceability Evidence Report allows you to demonstrate software traceability and requirements coverage, which is essential for meeting standards such as ISO 26262.
This package contains a tool extract tracing tags from ISO C or C++
source code. This tool is making use of a clang-tidy hack, and for
this to work you need to build our clang-tidy
fork and
place the clang-tidy binary somewhere on your PATH.
Instructions for clang-tidy here.
This tool works using a custom clang-tidy checker lobster-trace
which emits tracing information as clang checks.
We plan to rework this tool to be a stand-alone clang tool in the future.
Tools
lobster-cpp: Extract requirements from C/C++ code using a clang-tidy hack
Usage
This tool supports C/C++ code.
For this you can embedd tracing tags like this:
#include <string>
class Potato {
public:
std::string potato() {
// lobster-trace: something.example
return "potato";
}
};
You can add justifications as well:
#include <string>
class Potato {
public:
std::string potato() {
// lobster-exclude: Reason to justify the exlude
return "potato";
}
};
Copyright & License information
The copyright holder of LOBSTER is the Bayerische Motoren Werke Aktiengesellschaft (BMW AG), and LOBSTER is published under the GNU Affero General Public License, Version 3.
Metadata
Release files for bmw-lobster-tool-cpp 1.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bmw_lobster_tool_cpp-1.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Release files / bmw_lobster_tool_cpp-1.0.6-py3-none-any.whl
| Download URL | bmw_lobster_tool_cpp-1.0.6-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6163608bc0819236fe7a5ba467601b87f7a95ff5bb872929f6137c433884508d
|
|
BLAKE2b-256 checksum How to use checksums |
aa48dcba6c289769d5411b4b4f5b82c28a257ac08166a421fcfe4debc8c2829e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency log