Skip to content

Latest commit

 

History

History
45 lines (29 loc) · 1.7 KB

README.md

File metadata and controls

45 lines (29 loc) · 1.7 KB
Raw

chromium-vulnerabilities

Data for vulnerabilityhistory.org

Travis Build Build Status

Every push and pull request is run against our integrity checkers on Travis. Click on the above tag to see the status of the build.

For SWEN 331 Students

Please see the assignments folder for information about your project.

Get the Git Log data for commits/gitlog.txt

Use this git command to generate the git log:

git log --pretty=format:":::%n%H%n%an%n%ae%n%ad%n%P%n%s%n%b%n;;;" --stat --stat-width=300 --stat-name-width=300 --ignore-space-change

This gets absolutely everything, so don't commit that file - but cut it down to the commits you need. We're working on automating this.

Here's an example of just one commit:

$ cd tmp/v8
$ git log -1 --pretty=format:":::%n%H%n%an%n%ae%n%ad%n%P%n%s%n%b%n;;;" --stat --stat-width=300 --stat-name-width=300 --ignore-space-change 498b074bd0db2913cf2c9458407c0d340bbcc05e >> ..\..\commits\gitlog.txt

Here's how to get commits between VCC and fix (Windows cmd):

$ cd tmp/v8
$ git log --pretty=format:"%H" 498b074bd0db2913cf2c9458407c0d340bbcc05e..b32ff09a49fe4c76827e717f911e5a0066bdad4b -- src/regexp.js > ../commit_hashes.txt
$ for /F %i in (../commit_hashes.txt) do git log -1 --pretty=format:":::%n%H%n%an%n%ae%n%ad%n%P%n%s%n%b%n;;;" --stat --stat-width=300 --stat-name-width=300 --ignore-space-change %i >> ..\..\commits\gitlog.txt

Get the Releases data

Release data is scraped from this Wikipedia article

$ cd scripts
$ ruby get_releases.rb