Taking a quick look at the repository, there is no LICENSE file, which makes packaging practically impossible due to debian/copyright file requiring the contents etc. to specify who owns what etc.

@Arszilla Hi, we have added a license to our project

Setezor is a network traffic analyzer with the ability to automatically build network topology. It allows you to run active and passive scans and automatically draw L3 network map.

[Name] Setezor
[Version] 0.5.7b
[Homepage] https://github.com/lmsecure/Setezor
[Author] LMSecutity
[Licence] Mit
[Download] https://github.com/lmsecure/Setezor/releases
[Description] Setezor is a network traffic analyzer with the ability to automatically build network topology
[Dependencies] sudo, libcap2-bin, python3.11, python3.11-dev, python3-pip, python3.11-venv, nmap, masscan
[Activity] The network is actively developing and updates are constantly being released for it. In the future, it is planned to expand the functionality and add pentest and osint modules.
[How To Use] Usage examples are included in the README.MD

@kali-team, please could this be packaged up.
@author, If you want to help the packaging process, you can check the documentation here:

• https://www.kali.org/docs/development/setting-up-packaging-system/
• https://www.kali.org/docs/development/intro-to-packaging-example/
• https://www.kali.org/docs/development/intermediate-packaging-example/
• https://www.kali.org/docs/development/advanced-packaging-example/
• https://www.kali.org/docs/development/rebuilding-a-package-from-source/
• https://www.kali.org/docs/development/packaging-apps-with-kaboxer/

@g0tmi1k Hello, our team has made changes to the repository, Debian files have been added. The package was built in accordance with the documentation. The readme has been updated, now it has instructions for installing from source, deb and from dockerhub.

Link to the latest deb release: https://github.com/lmsecure/Setezor/releases/download/0.5.8b/setezor_0.5.8b_all.deb

Taking a look at the work done, it is improper and lacks the work done in the various packaging articles:

• https://www.kali.org/docs/development/intro-to-packaging-example
• https://www.kali.org/docs/development/intermediate-packaging-example
• https://www.kali.org/docs/development/advanced-packaging-example

I dont understand you, because I make packaging by second link (https://www.kali.org/docs/development/intermediate-packaging-example). By path "https://github.com/lmsecure/Setezor/tree/master/debian" exist files to create package. Can you write details about mistakes?

1. Your copyright is outright wrong.
2. There does not seem to be a reason to use a "helper script" at all.
3. changelog is out of format and standard.
4. control file does not list the build dependencies properly
5. The descriptions are lackluster in the control file, in addition to the dependencies being formatted badly
6. Your rules file is improperly formatted. Doesn't have the necessary flags etc. for PyBuild
7. There is practically no reason to override dh_usrlocal typically.
8. In theory, you don't even need the preinst etc. scripts. dh-python/PyBuild should be taking care of most of it.

I don't have the time currently to even attempt to package this but I highly recommend you read the docs again.