synchronize gemnasium DB with Vuln DB so that we don't lose data

Problem to solve

Desired Outcome: Migration / Archive plan needed

As we attempt to archive gemnasium original code and rewrite or migrate relevant parts it was identified that in order to identify "out of date" dependencies we need the genmasium data as that data is not in the new vulnerability database.

we also need to come up with synchronization and data storage plans so we don't lose gemnasium data.

from 2019-11-11 weekly secure composition analysis meeting.

Intended users

Further details

Proposal

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references