EclipseFdn / EclipseFdn/open-vsx.org

Claiming namespace [Celigo]

Open
#13,229 1 comment 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

Celigo

### 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

- [ ] 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

- [x] 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

Namespace `Celigo` belongs to Celigo, Inc. (https://www.celigo.com). I (`tylerlamparter`) work at Celigo, am a member of the `celigo` GitHub organisation, created this namespace and published its only extension.

Option 2 (Marketplace publisher, extension with no GitHub repo); validation by email from the company domain.

- Open VSX: https://open-vsx.org/extension/Celigo/celigo — published by GitHub ID `tylerlamparter`, the same ID making this request.
- VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=Celigo.celigo under publisher https://marketplace.visualstudio.com/publishers/Celigo. Its manifest has no `repository` field because the source is in a private repository of the `celigo` organisation.
- Domain: celigo.com. I will email openvsx@eclipse-foundation.org from my @celigo.com address quoting this issue's URL and comment here once sent.

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the namespace-claim checklist and verify the linked Open VSX and VS Code Marketplace publisher pages. Confirm the claimant's identity and required email evidence, then use the issue and follow-up comment as the completion record.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.