Static library automatically links with app even if package dependency is added in a particular framework

Recently I have been trying to add some package dependencies to a framework with mach-o type static library. The app compiles successfuly but when linking it is giving me duplicate symbol errors for all the symbols in added package. On closer inspection, I observed that the package library targets are being linked as .o with my app as well as framework binary. I have not added package targets in Link Binaries of my app's Build Phases. Xcode is doing it implicitly. I want to explicitly link with the framework.

Is there a way to stop linking package's .o with app?
Also why is the static library type of package .o and not .a?