when installing covenant-kbx or zenmap-kbx on a fresh install I receive this error.

┌──(root㉿kali)-[/home/kali]
└─# apt install covenant-kbx
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
covenant-kbx
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/26.1 MB of archives.
After this operation, 26.4 MB of additional disk space will be used.
Selecting previously unselected package covenant-kbx.
(Reading database ... 625818 files and directories currently installed.)
Preparing to unpack .../covenant-kbx_0.6-0kali7_amd64.deb ...
Unpacking covenant-kbx (0.6-0kali7) ...
Setting up covenant-kbx (0.6-0kali7) ...
Traceback (most recent call last):
File "/usr/bin/kaboxer", line 33, in <module>
sys.exit(load_entry_point('kaboxer==1.1.2', 'console_scripts', 'kaboxer')())
File "/usr/lib/python3/dist-packages/kaboxer/init.py", line 2204, in main
kaboxer.go()
File "/usr/lib/python3/dist-packages/kaboxer/init.py", line 363, in go
self.args.func()
File "/usr/lib/python3/dist-packages/kaboxer/init.py", line 1313, in cmd_upgrade
self.prepare_or_upgrade(self.args.app, upgrade=True)
File "/usr/lib/python3/dist-packages/kaboxer/init.py", line 1354, in prepare_or_upgrade
current_apps, registry_apps, tarball_apps, available_apps = self.list_apps(
File "/usr/lib/python3/dist-packages/kaboxer/init.py", line 1633, in list_apps
curmax = max(
File "/usr/lib/python3/dist-packages/kaboxer/init.py", line 1634, in <lambda>
app["versions"], default=None, key=lambda x: parse_version(x)
File "/usr/lib/python3/dist-packages/packaging/version.py", line 52, in parse
return Version(version)
File "/usr/lib/python3/dist-packages/packaging/version.py", line 197, in init
raise InvalidVersion(f"Invalid version: '{version}'")
packaging.version.InvalidVersion: Invalid version: 'latest'
Processing triggers for kali-menu (2022.4.1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for mailcap (3.70+nmu1) ...
Scanning processes...
Scanning candidates...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

Restarting services...
Service restarts being deferred:
systemctl restart docker.service

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.