# Compatibility between MOPS and Vessel?

**URL:** <https://forum.dfinity.org/t/compatibility-between-mops-and-vessel/25002>\
**Category:** Motoko\
**Created:** [November 25, 2023, 8:01pm UTC](https://forum.dfinity.org/t/compatibility-between-mops-and-vessel/25002 "2023-11-25T20:01:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![qwertytrewq](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/qwertytrewq/32/10423_2.png) [@qwertytrewq](https://forum.dfinity.org/u/qwertytrewq)\
**Post date:** [November 25, 2023, 8:01pm UTC](https://forum.dfinity.org/t/compatibility-between-mops-and-vessel/25002/1 "2023-11-25T20:01:30Z")

</div>

Can I use MOPS and Vessel package managers together? I mean: Not every package supports MOPS (AFAIK), how then use MOPS for such packages that support Vessel only?

So, what can you generally comment about compatibility between MOPS and Vessel?

Oh, fro [here](https://forum.dfinity.org/t/mops-on-chain-package-manager-for-motoko/17275):

> Recently, MOPS also supports installing packages from GitHub and vessel configuration (thanks to @tomijaga)  
> `mops i https://github.com/dfinity/motoko-base`

How far this compatibility goes? Is it seamless? Any underwater obstacles? Is MOPS therefore a complete replacement for Vessel?

---

<div class="post-metadata">

**Author:** ![Vivienne](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/vivienne/32/29170_2.png) [@Vivienne](https://forum.dfinity.org/u/Vivienne)\
**Post date:** [November 27, 2023, 9:30am UTC](https://forum.dfinity.org/t/compatibility-between-mops-and-vessel/25002/2 "2023-11-27T09:30:55Z")

</div>

AFAIK development on Vessel has stopped because MOPS is so much better. I would suggest you don’t bother with Vessel anymore if it’s avoidable
