Skip to content

Restructuring mega-foss data #101

@andymeneely

Description

@andymeneely

Here's what we need:

  • lists/repos.csv - List of GitHub repositories that we know are traced to a vulnerability. The identifier for a repo should be nameorg/reponame. For example, if this repo was on the list, it would be identified as VulnerabilityHistoryProject/mega-foss and then to clone it would be this: git clone https://github.com/VulnerabilityHistoryProject/mega-foss.git. We currently have a bunch of lists in this repo. Let's combine them all.
  • A script that runs on the RC cluster that will clone all of the repos from lists/repos.csv into /shared/rc/sfs/mega-foss-repos. If the script gets interrupted, it should pick up where it left off (i.e. don't clone it again if you've already cloned it before). We want to run this script from time to time when we update our repo list.
  • Make a list of the filenames in lists that we no longer need on this issue.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions