jdom license classification not correct

[KrzysztofKlubek]

Description

I have a problem after updating trivy to 0.63, in 0.65 is the same. With java maven project and library org.jdom:jdom after running:
trivy filesystem --debug --config trivy-config.yaml ./
in output file license.json i have:

   {
    "Severity": "UNKNOWN",
     "Category": "unknown",
     "PkgName": "org.jdom:jdom",
     "FilePath": "pom.xml",
     "Name": "Similar to Apache License but with the acknowledgment clause removed",
     "Text": "",
     "Confidence": 1,
     "Link": ""
   },

in trivy-config-yaml I have in notice category, after my tries:

    - Similar to Apache License but with the acknowledgment clause removed        
    - "Similar to Apache License but with the acknowledgment clause removed"
    - "text://Similar to Apache License but with the acknowledgment clause removed"
    - "text://.* Similar to Apache License but with the acknowledgment clause removed `.*"

trivy in 0.62 gives output in license.json:

    {
      "Severity": "LOW",
      "Category": "notice",
      "PkgName": "org.jdom:jdom",
      "FilePath": "pom.xml",
      "Name": "Similar to Apache License but with the acknowledgment clause removed",
      "Text": "",
      "Confidence": 1,
      "Link": ""
    },

after update to 0.63 and above:

    {
      "Severity": "UNKNOWN",
      "Category": "unknown",
      "PkgName": "org.jdom:jdom",
      "FilePath": "pom.xml",
      "Name": "Similar to Apache License but with the acknowledgment clause removed",
      "Text": "",
      "Confidence": 1,
      "Link": ""
    },

How can I define category for this license?

Desired Behavior

Trivy should classify license as notice according to configuration in trivy-config.yaml

Actual Behavior

Trivy classify license as unknown

Reproduction Steps

1.create trivy-config.yaml with
    notice:
        - Similar to Apache License but with the acknowledgment clause removed        
        - "Similar to Apache License but with the acknowledgment clause removed"
2.create java maven project with org.jdom:jdom library in pom.xml
3.run trivy.exe filesystem --config trivy-config.yaml ./
...

Target

Filesystem

Scanner

License

Output Format

JSON

Mode

Standalone

Debug Output

.

Operating System

linux

Version

Version: 0.63.0
Version: 0.65.0

Checklist

• Run trivy clean --all
• Read the troubleshooting

[DmitriyLewen]

Hello @KrzysztofKlubek
Thanks for your report!

Created #9379

Also i wrote workaround in issue description.

Regards, Dmitriy

[KrzysztofKlubek]

thanks, it works