License should reflect OSL

Preconditions

1. Check license stated in composer.json for packages
2. Compare to license.txt

Steps to reproduce

1. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/AdvancedSearch/composer.json#L19
2. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Amqp/composer.json#L14
3. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/AsynchronousOperations/composer.json#L21
4. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Authorizenet/composer.json#L22
5. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Braintree/composer.json#L31
6. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Elasticsearch/composer.json#L21
7. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/EncryptionKey/composer.json#L14
8. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/MessageQueue/composer.json#L13
9. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/MysqlMq/composer.json#L14
10. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Paypal/composer.json#L32
11. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/ProductVideo/composer.json#L22
12. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Signifyd/composer.json#L23
13. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/SwaggerWebapiAsync/composer.json#L16
14. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Swatches/composer.json#L25
15. https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Vault/composer.json#L18

The following Core Bundled Extension
vertex/module-tax
is currently stated as proprietary but no further license details are provided.

Expected result

1. license in composer.json should read

    "license": [
        "OSL-3.0",
        "AFL-3.0"
    ],

Actual result

1. proprietary

[magento-engcom-team]

Hi @fooman. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me {$VERSION} instance

where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.

@fooman do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[engcom-backlog-nickolas]

Hello @fooman, thank you for your report.
We've acknowledged the issue and added to our backlog.

[sidolov]

Hi @fooman. Thank you for your report.
The issue has been fixed in #17268 by @mhauri in 2.3-develop branch
Related commit(s):

• 90134aef95bdd3689f8236eab233b09e6c84a9a1
• 0d5cb1e4d2f74eab03c637c68cb820e5adab75e0

The fix will be available with the upcoming 2.3.0 release.