[New Snap] GasBuddy Crypto

Open
  • Is something wrong?
#1,547 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
security, tooling

Research direction

Start by reviewing the linked GasBuddy Crypto Snap repository and npm package, then determine what audit evidence and vulnerability details are required for this registry. Document the audit findings, link fixes for vulnerabilities that need remediation, and explain why any others do not; done also requires the corresponding pull request in this repository to be merged.

Written by the indexing model from the issue text.

Description

allowlist allowlist-new-snap

Checklist

All items in the list below needs to be satisfied.

  • Is the Snap repository publicly accessible and linked in this ticket? https://github.com/MariyaSoulo/gasbuddycrypto-snap
  • Is the Snap distributed on npm and linked in this ticket? https://www.npmjs.com/package/gasbuddycrypto-snap
  • 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.
Dominant language
TypeScript
Stars
53
Forks
29
Avg merge
1d 22h
Merged PRs (30d)
5

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MetaMask/snaps-registry

All issues in MetaMask/snaps-registry

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.