Move hackeroneIdentifier from retire.js to analyzers common library
Problem to solve
The purpose of this issue is to move the hackeroneIdentifier
function from the retire.js project to the Analyzers Common Library.
Intended users
Further details
This change will enable multiple analyzers, such as Retire.js and gemnasium to both use the hackeroneIdentifier
function, for example to allow de-duplicating similar vulnerabilities.
Proposal
-
Add hackeroneIdentifier
to identifier.go in the common library and implement unit tests -
Remove hackeroneIdentifier
from the retire.js project and use the function from the common library -
Add a test to one of the test projects which shows that the new hackeroneIdentifier
function works as expected
What does success look like, and how can we measure that?
Using retire.js on a project which invokes the hackeroneIdentifier
function from the common library works as expected.
What is the type of buyer?
Links / references
Edited by Fabien Catteau