MetaMask / MetaMask/snaps-registry
[New Snap] Namebase
Open
Nobody has claimed this yet.
allowlist
allowlist-new-snap
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 29
- Avg merge
- 10h 9m
- Merged PRs (30d)
- 3
Description
Checklist
All items in the list below needs to be satisfied.
- Is the Snap repository publicly accessible and linked in this ticket? https://git.eskimo.dev/namebase/metamask
- Is the Snap distributed on npm and linked in this ticket? https://www.npmjs.com/package/@namebase.io/metamask
- Has an audit been performed and the audit report attached or linked in this issue? n/a
- Is a complete list of discovered vulnerabilities from the audit documented in this issue?
- For vulnerabilities that have been deemed necessary to be addressed, are the links to the fixes attached to this issue?
- For vulnerabilities that have been deemed not necessary to be addressed, is a reason for each of them documented in this issue?
- The corresponding pull request in this repo has been merged.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Snap repository and npm package, then verify the audit status and any documented vulnerabilities or fixes. The work is complete when the required security information is attached or explained and the corresponding pull request in this repository has been merged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100