You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Clarify licensing for plugins/upgrade-agent (plugin.json vs repository LICENSE.md) #22
I noticed what appears to be a discrepancy and would appreciate some clarification on which license applies.
The plugins/upgrade-agent/plugin.json file declares:
"license": "MIT"
However, the repository's root LICENSE.md contains the Microsoft Pre-Release Software License Terms rather than the MIT License.
Additionally:
plugin.json points to this repository as both the repository and homepage.
There does not appear to be a separate LICENSE file under plugins/upgrade-agent/.
Question
Could you clarify which license applies to the upgrade-agent plugin?
If the plugin is intended to be MIT licensed, would it be possible to include the corresponding license file or documentation? Otherwise, if the repository's pre-release license is intended to apply, should the license field in plugin.json be updated accordingly?
This clarification would help users and compliance/license-scanning tools correctly determine the applicable license.
Activity