process: initial security management process

[masc2023]

Resolves: #709, #696

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ✅ Passed

Click to expand output

[License Check Output]
2025/04/10 16:19:40 Downloading https://releases.bazel.build/7.4.0/release/bazel-7.4.0-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (90 packages loaded, 10 targets configured)

Analyzing: target //:license-check (98 packages loaded, 10 targets configured)

Analyzing: target //:license-check (125 packages loaded, 782 targets configured)

Analyzing: target //:license-check (131 packages loaded, 823 targets configured)

Analyzing: target //:license-check (145 packages loaded, 2237 targets configured)

Analyzing: target //:license-check (145 packages loaded, 2465 targets configured)

Analyzing: target //:license-check (146 packages loaded, 2465 targets configured)

Analyzing: target //:license-check (149 packages loaded, 4611 targets configured)

INFO: Analyzed target //:license-check (150 packages loaded, 4737 targets configured).
[3 / 12] Creating source manifest for @@dash_license_checker~//tool/formatters:dash_format_converter [for tool]; 0s local
[9 / 13] JavaToolchainCompileClasses external/rules_java~/toolchains/platformclasspath_classes; 0s processwrapper-sandbox ... (2 actions running)
[11 / 13] JavaToolchainCompileBootClasspath external/rules_java~/toolchains/platformclasspath.jar; 0s processwrapper-sandbox
[12 / 13] Building license.check.license_check.jar (); 0s multiplex-worker
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 21.835s, Critical Path: 2.74s
INFO: 13 processes: 9 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 13 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt -review -project automotive.score -repo https://github.com/eclipse-score/score -token otyhZ4eaRYK1tKLNNF-Y
[main] INFO Querying Eclipse Foundation for license data for 76 items.
[main] INFO Found 52 items.
[main] INFO Querying ClearlyDefined for license data for 24 items.
[main] INFO Found 24 items.
[main] INFO Vetted license information was found for all content. No further investigation is required.

[github-actions]

The created documentation from the pull request is available at: docu-html

[pahmann]

Is there any reasoning behind the re-ordering of process areas? (I am just asking, it is not a finding to change this.)

[masc2023]

Just some thinking in Project Management activities, including Safety/Security and Change Request first, then Problem and finally more Infrastructure Config, Tool, Release, but open to discuss different orders