Here’s an alternative approach using SPDX 2.3 format, tested with Automation Studio 4.12.
The PowerShell script scans the project structure (Cpu.sw, Cpu.pkg, .hw, .prg, .lby files) and generates one .spdx.json per hardware configuration. It captures
Automation Runtime, VC Firmware, Technology Packages, Tasks (with version from .prg files), Libraries, and Hardware Modules.
I directly tried it out with my github Community project which is AS4.12, very cool!
Thanks a lot for sharing it!!
Maybe you want to split your post into a new thread? I think it’s worth to place it a bit more “prominent”
Just as a hint for others who want to try / test:
as the script is not signed, probably the execution is blocked / prohibited because of the execution policy of power shell.
It happened on my company device, so I checked it with my private W11 device.
But even there, the standard policy blocked the script run. As I’m fortunately administrator of my private owned device, I was able to change the execution policy just by right-click on the .ps1 file, choose properties → “Allow” (translated from German, I’m not sure how it’s exactly named in English Windows versions, pls see screenshot).