There is 1 open security issue in sid.
commit b0bc109d3bbc9672ee29111cbff5720c3458840b Author: Ondřej Nový <onovy@debian.org> Date: Thu Sep 24 08:47:07 2020 +0200 d/control: Update Vcs-* fields with new Debian Python Team Salsa layout commit e49f24383c51fad7be02d2779c50b8aa18b12927 Author: Ondřej Nový <onovy@debian.org> Date: Thu Sep 24 08:47:07 2020 +0200 d/control: Update Maintainer field with new Debian Python Team contact address commit b91c77c4a3f2c316892b991d30b8ff420812577a Merge: bb29ffc 00e031e Author: Jelmer Vernooij <jelmer@debian.org> Date: Mon Jan 13 22:02:20 2020 +0000 Merge branch 'lintian-fixes' into 'debian/master' Fix some issues reported by lintian See merge request python-team/modules/python-cmarkgfm!1 commit 00e031eee322f2d0ec5427261ca01ba093083fc1 Author: Debian Janitor <janitor@jelmer.uk> Date: Tue Jan 7 16:08:52 2020 +0000 Update standards version to 4.1.5, no changes needed. Fixes: lintian: out-of-date-standards-version See-also: https://lintian.debian.org/tags/out-of-date-standards-version.html commit 4b8179e3adf432322fc604b4a7f6c1c1e5d198e7 Author: Debian Janitor <janitor@jelmer.uk> Date: Tue Jan 7 16:08:29 2020 +0000 Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. Fixes: lintian: upstream-metadata-file-is-missing See-also: https://lintian.debian.org/tags/upstream-metadata-file-is-missing.html commit 766547084227668d13d9290ebb8de3a50bc3c3c7 Author: Debian Janitor <janitor@jelmer.uk> Date: Tue Jan 7 16:08:04 2020 +0000 Bump debhelper from old 11 to 12. Fixes: lintian: package-uses-old-debhelper-compat-version See-also: https://lintian.debian.org/tags/package-uses-old-debhelper-compat-version.html commit bb29ffcf4a1b5d1e685813971744766ae1823fd9 Author: Ondřej Nový <onovy@debian.org> Date: Sun Aug 25 11:01:46 2019 +0200 d/control: Fix wrong Vcs-* commit 1b0f0c41e0bbcff1955be9085e221db1d0d7d120 Author: Ondřej Nový <onovy@debian.org> Date: Fri Jul 19 23:44:29 2019 +0200 Use debhelper-compat instead of debian/compat
There is 1 open security issue in buster.
You can find information about how to handle this issue in the security team's documentation.