rename published advisories to full HSEC id (fix OSV export)

[frasertweedale]

A quick attempt at fixing the OSV export after the repo reorg landed.

Current OSV export after landing the reorg change (#293 ) disappeared a bunch of the advisories:

commit 364d85e0dfb0e0ffa3a7e9f90f41d7a756ddde66 (origin/generated/osv-export)
Author: Haskell Security Response Team <security-advisories@haskell.org>
Date:   Fri Nov 14 13:02:12 2025 +0000

    2025-11-14 13:02:12+00:00 (fb4be1123d3ef5606703026c5949e2cc58e2a800)

 0001/0001.json           | 1 +
 0002/0002.json           | 1 +
 0003/0003.json           | 1 +
 0004/0004.json           | 1 +
 0005/0005.json           | 1 +
 0006/0006.json           | 1 +
 0007/0007.json           | 1 +
 0008/0008.json           | 1 +
 0009/0009.json           | 1 +
 0010/0010.json           | 1 +
 0011/0011.json           | 1 +
 0012/0012.json           | 1 +
 0013/0013.json           | 1 +
 0014/0014.json           | 1 +
 0015/0015.json           | 1 +
 2023/HSEC-2023-0001.json | 1 -
 2023/HSEC-2023-0002.json | 1 -
 2023/HSEC-2023-0003.json | 1 -
 2023/HSEC-2023-0004.json | 1 -
 2023/HSEC-2023-0005.json | 1 -
 2023/HSEC-2023-0006.json | 1 -
 2023/HSEC-2023-0007.json | 1 -
 2023/HSEC-2023-0008.json | 1 -
 2023/HSEC-2023-0009.json | 1 -
 2023/HSEC-2023-0010.json | 1 -
 2023/HSEC-2023-0011.json | 1 -
 2023/HSEC-2023-0012.json | 1 -
 2023/HSEC-2023-0013.json | 1 -
 2023/HSEC-2023-0014.json | 1 -
 2023/HSEC-2023-0015.json | 1 -
 2024/HSEC-2024-0001.json | 1 -
 2024/HSEC-2024-0002.json | 1 -
 2024/HSEC-2024-0003.json | 1 -
 2024/HSEC-2024-0006.json | 1 -
 2024/HSEC-2024-0007.json | 1 -
 2024/HSEC-2024-0008.json | 1 -
 2024/HSEC-2024-0009.json | 1 -
 2025/HSEC-2025-0001.json | 1 -
 2025/HSEC-2025-0002.json | 1 -
 2025/HSEC-2025-0003.json | 1 -
 2025/HSEC-2025-0004.json | 1 -
 2025/HSEC-2025-0005.json | 1 -
 42 files changed, 15 insertions(+), 27 deletions(-)

---

Advisory

• It's not duplicated
• All fields are filled
• It is validated by hsec-tools

hsec-tools

• Previous advisories are still valid

[frasertweedale]

OK, that seems to have fixed it:

commit b925f71eb1496adc671241b64fd9a6de43b36ec9 (origin/generated/osv-export)
Author: Haskell Security Response Team <security-advisories@haskell.org>
Date:   Fri Nov 14 14:47:44 2025 +0000

    2025-11-14 14:47:44+00:00 (d66028837a97d77a9ada5b55c985b3e4476fe140)

 2023/HSEC-2023-0001.json                   | 1 +
 2023/HSEC-2023-0002.json                   | 1 +
 2023/HSEC-2023-0003.json                   | 1 +
 0004/0004.json => 2023/HSEC-2023-0004.json | 2 +-
 0005/0005.json => 2023/HSEC-2023-0005.json | 2 +-
 2023/HSEC-2023-0006.json                   | 1 +
 2023/HSEC-2023-0007.json                   | 1 +
 2023/HSEC-2023-0008.json                   | 1 +
 2023/HSEC-2023-0009.json                   | 1 +
 0010/0010.json => 2023/HSEC-2023-0010.json | 2 +-
 0011/0011.json => 2023/HSEC-2023-0011.json | 2 +-
 0012/0012.json => 2023/HSEC-2023-0012.json | 2 +-
 0013/0013.json => 2023/HSEC-2023-0013.json | 2 +-
 0014/0014.json => 2023/HSEC-2023-0014.json | 2 +-
 0015/0015.json => 2023/HSEC-2023-0015.json | 2 +-
 0001/0001.json => 2024/HSEC-2024-0001.json | 2 +-
 0002/0002.json => 2024/HSEC-2024-0002.json | 2 +-
 0003/0003.json => 2024/HSEC-2024-0003.json | 2 +-
 0006/0006.json => 2024/HSEC-2024-0006.json | 2 +-
 0007/0007.json => 2024/HSEC-2024-0007.json | 2 +-
 0008/0008.json => 2024/HSEC-2024-0008.json | 2 +-
 0009/0009.json => 2024/HSEC-2024-0009.json | 2 +-
 2025/HSEC-2025-0001.json                   | 1 +
 2025/HSEC-2025-0002.json                   | 1 +
 2025/HSEC-2025-0003.json                   | 1 +
 2025/HSEC-2025-0004.json                   | 1 +
 2025/HSEC-2025-0005.json                   | 1 +
 27 files changed, 27 insertions(+), 15 deletions(-)

[frasertweedale]

ah, human_links are all busted now. I will fix in a new PR.

[frasertweedale]

also of note: the switch to symbolic links has broken the "modified time" lookup, as it uses the git repo. We need to deref the symlink and then find out the modified time of the canonical file. But of course, that will be broken now too, because it is a new file.

It might be time to find a new way of storing/calculating the publication and modification times of advisories.

[frasertweedale]

human_link fix: #302