<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Issue</th>
<td>
<a href=https://github.com/llvm/llvm-project/issues/96039>96039</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>
The LLVM security group should archive data on chromium.org
</td>
</tr>
<tr>
<th>Labels</th>
<td>
new issue
</td>
</tr>
<tr>
<th>Assignees</th>
<td>
</td>
</tr>
<tr>
<th>Reporter</th>
<td>
kbeyls
</td>
</tr>
</table>
<pre>
For the past 4 years, the LLVM project has been using https://bugs.chromium.org/p/llvm/issues/list?q=&can=1 to enable people to report security issues to the LLVM security group.
We have recently moved away from using chromium.org to using [github for reporting security issues](https://llvm.org/docs/Security.html#how-to-report-a-security-issue).
We expect that the chromium.org issue tracker may not retain the past issues raised forever, so we should find a way to archive the data somehow. Our past transparency reports refer to the chromium issues, so if the issues went away, we'd loose historical data.
This ticket covers finding a fit-for-purpose way to archive the historical tickets.
@llvm/llvm-security-group
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJxslMGTqzYMxv8ac9GEAUMCHDi810xO2-mhO-3ZgIjdBUxlkZT_vmNDNps3e8pEGn_5fZ-kKOfMdUKsxfGnOJ4jtbC2VH80uA4uamy31hdLwBphVo4hhxUVOSF_C7W3t79-h5nsP9gyaOWgQZxgcWa6gmaench-CHkR8tIsVxe3muxoljG2dBXyMgt5GYbbKOTFOLeg89-NY5Fd_hXZWchTqyaRnVNgCzipZkCY0c4D-gLhbInBYbuQ4RU2Cd_5JPvsXckucyySs0h-_I2g1Q2BsMWJhxVGe8MO1F2t0JMdd_yvrF50q4rjz6thvTTQW9oRfP0XCnE8C1m-JuCd7sY723qvf-6PYs3jIGSm7f3A9rCpHtThIXoIokJWu4NPH_jf7INnrTiYfmEOj4BJtR9IMKoVJstAyMpMz4HuqZEyDjtvCm9IfrzOwh3BabsMHfRm6kCBj4gtKGq1uWEQ6RQrcHZEbe8x_LHQJsukJjcrwqld95gcEPZIjwE9WB-JbT9p-tDcqe44cRiM795RyKKDwVqHoI1jS6ZVQyB4CeZdGwds2g9kaO0NyQV-PyYFveFDb-kwLzR7oW8sfdHeVNyLvMiTfWn9x3NIYccg6uqsq7JKRVinRVoWZV5UaaTrRuZHiaeyLUqVVbIoujTLMK2yoqqyqiwjU8tE5skprZIyzdI0xgq7RpZdjj3K_FiJPMFRmSF-bFIUYqqrU5JV0aAaHFy4YyknvMO-NNKfNdWB1R-hxzeO3VOFDQ9Yv39_NI8NeAQU5m2nl1WLFhrq12XfjiRu7fi88YCw_1l8PfmN_1bL_wMAAP__4sKOig">