Kali is a rolling release, no backport

From the md5sum, it seems that the amd64 .deb is taken as-is from Debian buildd.

Correct.

Is it possible to triggrer a systematic rebuild on Kali infrastructure.

We don't do that so far, AFAIK. We never had this case.

We can fork the package for the sake of rebuilding it, but then updates are manual on our side, so it's a bit of recurring work.

Ok I will ship the same .deb for both OS.

What is the easiest way to check for Kali at runtime ?

A stat on /etc/dpkg/origins/kali ?

I will check if libdpkg provides tag

If you can do the check at runtime, indeed it works better for us.

Yes you can check dpkg origin:

# ls -l  /etc/dpkg/origins/
total 8
-rw-r--r-- 1 root root 83 Jun 16 10:14 debian
lrwxrwxrwx 1 root root  4 Jun 28 04:01 default -> kali
-rw-r--r-- 1 root root 91 Jun 16 10:14 kali

That works also for Ubuntu:

# ls -l /etc/dpkg/origins/
total 8
-rw-r--r-- 1 root root  83 Apr 20 08:46 debian
lrwxrwxrwx 1 root root   6 Apr 21 02:05 default -> ubuntu
-rw-r--r-- 1 root root 114 Apr 20 08:46 ubuntu

Thank you for the support.

I've uploaded cruft-ng 0.9.87 that test for /etc/dpkg/origins/kali at runtime

You may close this bug

Kali linux packages are encoraged to use dh-cruft to register the volatiles files
that should (or not) be removed on purge phase, this would
relieve me from maintaining shadow-rules upstream; but that's a wish-list priority.

If doing so we could start with "wordlists" which looks is a simple package.