Broken timestamp in a vulnerability record (except if we discovered it 2024 year ago ;-)

[adulau]

It seems there is a record with a broken modified date 001-01-01T00:00:00Z

• advisory-database/vulns/cipherbcrypt/PYSEC-2024-55.yaml

  Line 4 in 0676e94

  affected:

We discovered it while importing it in vulnerability-lookup.

and we were wondering why there are no published record too.

[di]

Hmm, looks like the GitHub workflow failed. @sethmlarson you added this in #184, mind taking a look?