Skip to content

fix: Resolve parsing of packages from dependency path that start with @

What does this MR do?

Fixed the regex for parsing dependency paths for pnpm lock files in the v6 format if a dependency path is for a scoped package the parsing of name, version failed due to the occurence of two at-symbols.

This ended up the SBOM file that gets generated would not have its name-field populated

What are the relevant issue numbers?

gitlab-org/gitlab#336809 (closed)

Does this MR meet the acceptance criteria?

Edited by Adam Cohen

Merge request reports