jfrog / jfrog/frogbot

License violations don't include Severity. Also lots of licenses get reported as Unknown.

Open
#666 19 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
372
Forks
107
Avg merge
2d 20h
Merged PRs (30d)
5

Description

Describe the bug

When reporting license violations, severity is not reported, both in the PR scan as well as Repo scan. Xray on-demand scans do include severity information for licenses. Also, a lot of licenses are reported as Unknown when using a watch with policy to report Unknown licenses. Please see the screenshots uploaded in 'Current behaviour'.

Current behavior

In PR scan:
license_violations

In Repo scan:
repo_scan

Reproduction steps

Run Frogbot scans with a watch configured to report license violations along with unknown licenses.

Expected behavior

Severity is reported, so higher ones could be spotted over lower ones. There should not be too many unknown licenses, only legitimate cases should be reported.

JFrog Frogbot version

2.19.10

Package manager info

npm. package.json.

Git provider

GitHub

JFrog Frogbot configuration yaml file

No response

Operating system type and version

Github Actions. Ubuntu 22.04.4.

JFrog Xray version

3.87.9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with package.json and reproduce the PR and Repo scans in GitHub Actions using Frogbot 2.19.10, a watch configured for license violations and unknown licenses, and the npm package manager. Compare the results with the expected behavior: license violations show severity and only legitimate unknown licenses remain.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, go
Domain
ci-cd, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.