rkg-mm

This would address https://github.com/DependencyTrack/dependency-track/issues/2183, and I totally need this yesterday 😆 One idea: In the existing vulnerability analysis view, add a button like "Apply to all project versions", clicking it...

Simple solution proposal: If a group gets VIEW_BADGES Permission, ensure no other permission can be assigned additionally. If another one was assigned already, prevent assigning of VIEW_BADGES with some hint.

If you are not creating any managed users, nobody can login with user/pw. Why need to explicitly disable it?

I would highly appreciate this here, too. Going especially through NPM dependencies is a pain as I regularly see >60 vulnerabilities, but almost all from dev dependencies. Ideally I think...

> Hi [@rkg-mm](https://github.com/rkg-mm)! I'm not familiar with javascript. Could you please share your thought about why we often don't care the dev vulnerabilities? In my opinion, it seems that dev...

This is a planned feature with some draft available here https://github.com/DependencyTrack/frontend/pull/658. It still needs some work though.

@stevespringett Since this is something I need too, to be able to use some custom licenses in policies, how would you expect this to work in its easiest way? Would...

@stevespringett not sure if you got my idea, i wasn't thinking about integrating the other license sources. More useful for me is a way to just simply create my own...

How should this work if a project is assigned to multiple teams?

Love this, I need this :) Not sure if maintaining them as string is the best solution, but will leave this up to maintainers ;) But another note: I might...