# Why does my local package have access to all of my workspace's dependencies?

**URL:** <https://forums.swift.org/t/why-does-my-local-package-have-access-to-all-of-my-workspaces-dependencies/83651>\
**Category:** Package Manager\
**Tags:** spm, xcode, packagemanager\
**Created:** [December 10, 2025, 6:32am UTC](https://forums.swift.org/t/why-does-my-local-package-have-access-to-all-of-my-workspaces-dependencies/83651 "2025-12-10T06:32:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![BitByAVampire](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/bitbyavampire/32/36297_2.png) [@BitByAVampire](https://forums.swift.org/u/BitByAVampire)\
**Post date:** [December 10, 2025, 6:32am UTC](https://forums.swift.org/t/why-does-my-local-package-have-access-to-all-of-my-workspaces-dependencies/83651/1 "2025-12-10T06:32:48Z")

</div>

I have a local package that I created and add to my workspace, and it seems to be able to have access to all the dependencies added to my workspace, for example, ModuleA. Even though I did not declare Module A as a dependency in my package manifest file, the package can still find it and the package can use its apis and compile and build just fine with the project.

I find this strange because I thought the manifest file determined what dependencies a package can have access to.