Limit token scope

[AnHeuermann]

I have access to two different namespaces on Open VSX Registry, my personal namespace and a namespace used by an organization I'm a member of.
It would be great to limit the scope of the access tokens to specific namespaces and even better specific extensions. So if one personal access token leaks no other extensions I have access to is at risk.

So I want to use a unique token for my personal AnHeuermann/extension1 and two other unique tokens for organization/extension2 and organization/extension3.

[amvanbaren]

Hi @AnHeuermann! Thanks for the feature request. This would be a good enhancement.

[montyc123]

code of conduct[]#

[tomodachi94]

This is important to me. I typically automate my release flows using GitHub Actions. If my token is leaked, the only thing that should be compromised is just that extension.

It would also be good to scope the token to specific actions. Right now, a token can also create a new namespace, which is unnecessary for CI/CD automation.