EclipseFdn / EclipseFdn/open-vsx.org

Claiming namespace [bobrowsse-tech]

Open
#13,086 0 comments 0 reactions 0 assignees View on GitHub
namespace operations
Dominant language
TypeScript
Stars
394
Forks
145
Avg merge
2d 19h
Merged PRs (30d)
3

Description

### Namespace

bobrowsse-tech

### Ownership

- [x] The namespace is not currently owned on Open VSX (verify by a search on [open-vsx.org](https://open-vsx.org))

### Account Age

- [x] The GitHub ID making this request has at least 12 months of public history

### VS Code Publisher with Repo

- [x] The namespace is also a publisher account on the VS Code Marketplace (check by browsing https://marketplace.visualstudio.com/publishers/{publisher}) and has an extension published there with a repo specified in its package.json file.

### VS Code Publisher without Repo

- [ ] The namespace is also a publisher account on the VS Code Marketplace and does not have published extensions or has published extensions with no GitHub repos.

### Not a VS Code Marketplace Publisher

- [ ] The namespace is not a publisher account on the VS Code Marketplace

### All Other Cases

- [ ] You are unable to provide the inputs required in the three options above. This option will take the longest to process.

### Claim evidence

Marketplace publisher: https://marketplace.visualstudio.com/publishers/bobrowsse-tech
Marketplace listing: https://marketplace.visualstudio.com/items?itemName=bobrowsse-tech.design-token-extractor-migrator
Open VSX listing: https://open-vsx.org/extension/bobrowsse-tech/design-token-extractor-migrator
Source repo: https://github.com/bobrowsse-tech/design-token-extractor
package.json publisher: bobrowsse-tech
package.json name: design-token-extractor-migrator
The extension repo is public and owned by the GitHub ID making this request (bobrowsse-tech / same account).
https://github.com/bobrowsse-tech/design-token-extractor

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the linked Open VSX and VS Code Marketplace listings, the source repository, and package.json to verify that the namespace is unowned and the publisher and repository details match. Done means confirming the claim evidence and processing the namespace request; no source file or test is identified in the issue.

Written by the indexing model from the issue text.

Assessment

Domain
devtools
Issue type
Feature
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.