Currently, Snyk vulnerability data ingested into Port does not differentiate between branches. As a result, teams cannot track branch-specific vulnerabilities or assess security posture across different development/release branches.

Proposed Solution / Requirements:

Ingest Snyk project/vulnerability data with associated branch or target reference details (e.g., exposing .attributes.target_reference on the project mapping).

Allow filtering and mapping of Snyk vulnerabilities per branch.

Enable associating branch-level vulnerability metrics with individual branch entities or services in Port.

Value / Impact:

Provides visibility into branch-level security posture, allowing teams to identify vulnerabilities before merging into main branches and better align security tracking with their Git workflows.