Resolve "License Scanning metrics"

What does this MR do and why?

Use GitLab internal analytics to count project dependencies processed by License Scanning during a single scan.

  • dependencies being scanned (total)
  • dependencies with licenses extracted from the SBOM
  • dependencies with scan results
  • dependencies with no scan results (unknowns)

Group these counts per PURL type, and publish one event per PURL type.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Related to #465860

Merge request reports

Loading