[BUG] AGPL license is sometimes not reported as restrictive

I have following pom.xml file:

<project>
    <modelVersion>4.0.0</modelVersion>
    <groupId>g</groupId>
    <artifactId>a</artifactId>
    <version>0.0.1</version>

    <dependencies>
        <dependency>
            <groupId>org.json</groupId>
            <artifactId>json</artifactId>
            <version>20190722</version>
        </dependency>

        <dependency>
            <groupId>com.itextpdf</groupId>
            <artifactId>itextpdf</artifactId>
            <version>5.5.13</version>
        </dependency>

        <!-- <dependency>
            <groupId>com.google.code.gson</groupId>
            <artifactId>gson</artifactId>
            <version>2.8.5</version>
        </dependency> -->
    </dependencies>

    <licenses>
        <license>
            <name>Apache License, Version 2.0</name>
            <url>https://www.apache.org/licenses/LICENSE-2.0.txt</url>
            <distribution>repo</distribution>
            <comments>A business-friendly OSS license</comments>
        </license>
    </licenses>
</project>

com.itextpdf:itextpdf is licensed under restrictive AGPL license, however analysis shows 0 restrictive licenses.

When I add another package (com.google.code.gson:gson:2.8.5) to my stack, it suddenly shows 1 restrictive license. Although there doesn’t seem to be a way how to pin point which of the dependencies is the one with restrictive license.

VSCode(please complete the following information):

• OS: linux
• VSCode version 1.37.1
• Dependency Analytics Version 0.0.12

[yzainee-zz]

https://jira.coreos.com/browse/APPAI-906

[yzainee-zz]

This is not an issue.