actions/dependency-review-action

Different configuration per package type?

Opened this issue · 0 comments

Is your feature request related to a problem? Please describe.
Our licensing policies are different for frontend vs backend packages. We have repositories that contain both frontend and backend code and we are forced to use the more conservative policy with a large number of exceptions.

Describe the solution you'd like
Would it be possible to specify a configuration per package type? Or per file location (frontend/package.json vs backend/package.json)?