Merge branch 'main' of https://github.com/moverseai/vcpkg-sbom

README.md

@@ -61,11 +61,9 @@ vcpkg-sbom PATH/TO/PROJECT/vcpkg_installed
 | 2  | package name #3 |
 | ... | package name #N |
 
-Merging spdx:  ━━━━━━━━━━━━━━━━━━ 100% 0:00:00
-
-Extracting & merging copyrights ...      
-
-Merging copyrights:  ━━━━━━━━━━━━━━━━━━   0% -:--:--
+> Merging spdx:  ━━━━━━━━━━━━━━━━━━ 100% 0:00:00   
+> Extracting & merging copyrights ...    
+> Merging copyrights:  ━━━━━━━━━━━━━━━━━━   0% -:--:--
 
 > [!NOTE]  
 > The output file is a `SPDX-2.3` `SPDXRef-DOCUMENT` that merges all available `*.spdx.json` files from the manifest's installed packages.
@@ -131,4 +129,4 @@ options:
 > As indicated at the `vcpkg` [docs](https://learn.microsoft.com/en-us/vcpkg/reference/vcpkg-json#license):
 > _The licensing information provided for each package in the vcpkg registry represents Microsoft's best understanding of the licensing requirements. However, this information may not be definitive. Users are advised to verify the exact licensing requirements for each package they intend to use, as it is ultimately their responsibility to ensure compliance with the applicable licenses._
 
-While `vcpkg` offers a lot of information about licensing, this information should be scrutinized. Any tool that builds on top of this information provided by `vcpkg` is reliant on the legibility of the provided data, and should thus, be also scrutinized for correctness.
+While `vcpkg` offers a lot of information about licensing, this information should be scrutinized. Any tool that builds on top of this information provided by `vcpkg` is reliant on the legibility of the provided data, and should thus, be also scrutinized for correctness.