Using Python API

[Yesser-Belhajali]

Hello everyone,
I'm building a project on top of OpenSCAP and was considering using the Python bindings (python3-openscap / openscap_api.py) instead of shelling out to the oscap CLI, since callbacks (register_start_callback / register_output_callback) looked like a cleaner way to get structured, per-rule results.

I also noticed the last commit touching the swig/ folder is about 3 years old, with very little recent activity or documentation/examples for modern use cases (SDS handling, tailoring, etc.).
So my actual question: is this Python binding still a reliable, maintained option for a new project today, or has it effectively been left behind in favor of the CLI? Specifically:

Does anyone have a working, modern example of loading a full Source Data Stream (selecting datastream-id + xccdf-id) through this binding?
Is there a recommended replacement (Ruby binding? Direct C API? CLI-only?) for new projects that need programmatic access rather than parsing CLI output?
Is this binding still considered supported by the OpenSCAP team, or is it legacy/best-effort only?