The purpose of Shared Packages is to organize your Composer modules Shared Packages functionality gives developers more fine-grained control for organizing code. Developers that already have or envision having various products in their portfolio (whether they be extensions or themes) that share common code and libraries will want to take advantage of Shared Packages. This functionality allows developers to market their products as a set and increase their sales. A developer can specify, for example, that in order for customers to run extension B, customers must first purchase and install extension A. Creation of shared packages is relevant only for products for the Magento 2.0 platform. All shared code and shared libraries can be zipped and uploaded one-by-one (one zip file per module) via the “Shared Packages” tab. I recently submitted my magento 2 packages successfully with status Ready to use.
Magento Commerce and Open Source 2.2.1, 2.1.10 and 2.0.17 contain multiple security enhancements. Cross-Site Scripting (XSS). Local File Inclusion (LFI). Authenticated Admin user remote code execution (RCE) . Arbitrary File Delete vulnerabilities APPSEC-1325: Stored XSS in Billing Agreements Type : Cross-Site Scripting (XSS, stored) CVSSv3 Severity : 5.5 (Medium) Known Attacks : None Description : An administrator with limited privileges can create Billing Agreements with embedded cross-site scripting elements that can subsequently lead to a stored cross-site scripting attack. Product(s) Affected : Magento Open Source prior to 1.9.3.7, and Magento Commerce prior to 1.14.3.7, Magento 2.0 prior to 2.0.17,