EclipseFdn / EclipseFdn/open-vsx.org
Claiming namespace CognizTech
- Dominant language
- TypeScript
- Stars
- 394
- Forks
- 145
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
### Namespace
CognizTech
### 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
- [ ] 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
- [x] 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
The namespace CognizTech my domain cogniz.tech (namespace = domain with the dot dropped). A TXT record listing this issue's URL is defined at cogniz.tech — verify with dig TXT cogniz.tech +short. Corroborating: the account (usama04, GitHub member since 2016) is an admin of the GitHub organization CognizTech (https://github.com/CognizTech), which owns the extension's source repository (https://github.com/CognizTech/stoot — the repository field in the extension's package.json) and the project homepage (https://stateroot.dev/). Published extension: https://open-vsx.org/extension/CognizTech/stateroot. CognizTech is not a publisher on VS Code Marketplace.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking whether CognizTech is already owned on open-vsx.org and whether it is a VS Code Marketplace publisher. Verify the TXT record with `dig TXT cogniz.tech +short`, then inspect the linked GitHub organization and the `package.json` in `CognizTech/stoot`. Done means the ownership evidence is confirmed and the namespace claim can be processed.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100