Skip to content

Licensing concerns #1008

Open
Open
@hador

Description

Hi team,

I noticed that following this PR, this package (@vscode/vsce, MIT licensed) now depends on @vscode/vsce-sign which is under the Microsoft license instead.

The current setup makes the licensing for @vscode/vsce land in a grey area.

Are there any plans to align the two?

Thanks.

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions