DependencyTrack / DependencyTrack/dependency-track

License policies do not produce the expected result.

Open
#5,720 1 comment 0 reactions 0 assignees View on GitHub
defect in triage pending more information
Dominant language
Java
Stars
4.2k
Forks
811
Avg merge
8h 39m
Merged PRs (30d)
237

Description

### Current Behavior

I have added two different license policies to the project, but only the license violations that meet the first policy are being reported.

This works OK (limited to one project)
![Image](https://github.com/user-attachments/assets/7b0b67a3-5ae3-468b-9981-1320653e7a6b)

license group
![Image](https://github.com/user-attachments/assets/d2513f43-d2b3-440c-ba91-ef37d536e636)
This reports all non permissive licenses.

This second policy does not produce any results. (global)
![Image](https://github.com/user-attachments/assets/31886051-893c-49b0-b299-6230093c2289)

license group
![Image](https://github.com/user-attachments/assets/40b410a4-ed23-4453-b5e3-de91f61867db)

GPL 3.0.. licenses are not reported as a fail.

### Steps to Reproduce

1. Existing project with components and license information
2. Create 2 new policies as above to track used licenses
3. Refresh / load SBOM

### Expected Behavior

Results are received from both policies.
All GPL3.0.. licenses should also result a fails.

### Dependency-Track Version

4.13.4

### Dependency-Track Distribution

Container Image

### Database Server

PostgreSQL

### Database Server Version

16-alpine

### Browser

Google Chrome

### Checklist

- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.