In the first approach when deleting a package all dependent comparisons and mappings are automatically deleted too.
In a new iteration it should check for the dependencies and return an error with the dependencies if any where found. This should give the FE the option to display those and present a prompt to verify it should be deleted with its dependencies for sure. The FE than should be able to call the same endpoint again and override the check with a force flag.