DB publishing twice in the same day may produce unexpected results

[wagoodman]

When baking a DB and adding that value to the listing file there are two things to keep in mind when sorting the listing entries:

• the date the data was pulled (not when the DB was built)
• the random suffix for each DB uploaded

Today if you wanted to rebuild a DB and replace todays DB (by adding a new entry in front of the other) then it's random chance if you can do so:

{
  "built": "2023-09-18T01:23:18Z",
  "checksum": "sha256:ce75b915aad4afd07afa499d28f2b9857401d40fabd3cafc25e494d391a5f079",
  "url": "https://toolbox-data.anchore.io/grype/databases/vulnerability-db_v3_2023-09-18T01:23:18Z_c4b2ec45d1433ce7556a.tar.gz",
  "version": 3
}
{
  "built": "2023-09-18T01:23:18Z",
  "checksum": "sha256:2f54bd73618e2a5235263f4bd9f4533e732699aa5962268ec151a08664f12d16",
  "url": "https://toolbox-data.anchore.io/grype/databases/vulnerability-db_v3_2023-09-18T01:23:18Z_5e0fa851d64332a6dfcb.tar.gz",
  "version": 3
}

These two were build 10 hours apart from one another, but you cannot tell this since it's the data age that makes the timestamp. Instead we're relying on good ordering of the suffix (which is random!).