# Serious collection requirement violation of cisco.mso: undeclared dependency on cisco.nd (which isn't part of Ansible community package) **URL:** \ **Category:** Project Discussions\ **Tags:** requirements, cisco, dependencies, community-wg, steering-committee, galaxy-ng\ **Created:** [July 4, 2024, 9:29am UTC](https://forum.ansible.com/t/serious-collection-requirement-violation-of-cisco-mso-undeclared-dependency-on-cisco-nd-which-isnt-part-of-ansible-community-package/7039 "2024-07-04T09:29:22Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [July 5, 2024, 7:44pm UTC](https://forum.ansible.com/t/serious-collection-requirement-violation-of-cisco-mso-undeclared-dependency-on-cisco-nd-which-isnt-part-of-ansible-community-package/7039/6 "2024-07-05T19:44:38Z")
> [@lhercot](#): > > Do you know why the “import” checks in Sanity on both Galaxy and Automation Hub did not find this issue? Do you mean the sanity tests run in CI? My guess is that the cisco.nd collection was installed before running the sanity tests. The sanity tests kind of assume that only the collections that the collection depends on (and transitive dependencies) are installed, so if you install other collections that are not dependencies, the import sanity test will not flag this. I’m not sure whether Galaxy/AH actually run the import sanity tests: the galaxy importer which could run them does not install _any_ collection dependencies ([Galaxy importer: collection dependency handling](http://forum.ansible.com/t/3496)), so the results of these tests would be mostly unusable (except for collections that have zero collection dependencies). --- _[View the full topic](https://forum.ansible.com/t/serious-collection-requirement-violation-of-cisco-mso-undeclared-dependency-on-cisco-nd-which-isnt-part-of-ansible-community-package/7039)._