# Implicit dependencies declaration

**URL:** https://community.tuist.dev/t/implicit-dependencies-declaration/91
**Category:** Troubleshooting & how to
**Created:** [October 9, 2024, 11:08am UTC](https://community.tuist.dev/t/implicit-dependencies-declaration/91 "2024-10-09T11:08:17Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![PierreMardon](https://community.tuist.dev/user_avatar/community.tuist.dev/pierremardon/32/208_2.png) [@PierreMardon](https://community.tuist.dev/u/PierreMardon)
#### Post date: [January 13, 2025, 1:38pm UTC](https://community.tuist.dev/t/implicit-dependencies-declaration/91/8 "2025-01-13T13:38:26Z")

</div>

> [@pepicrft](#):
>
> If they are not made private, you’ll be able to access them, for example if `Dynamic A` uses them in a public API. Exactly from the eyes of the app or the extension, C is a transitive dependency.

tbs, how do you make static framework (nested in dynamic framework) symbols private? Is keeping them unused publicly enough?

I’m asking because I can import the static framework as soon as I’m in a context that depends on the dynamic one (because of transitive deps). Am I missing some way of keeping the static framework narrowed to the private scope of the dynamic framework?

(this is related to my question [here](https://community.tuist.dev/t/privacy-of-static-libs-nested-inside-a-dynamic-framework/314), but I thought it would help anyone in a similar situation finding this post).

---

_[View the full topic](https://community.tuist.dev/t/implicit-dependencies-declaration/91)._