npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

wallet-guard-snap

v1.1.1

Published

Protect your crypto with transaction insights and proactive security alerts.

Downloads

409

Readme

Wallet Guard Snap

Installation Guide

Published build (recommended)

Please visit https://walletguard.app/snap for everything you need to get started using this Snap.

All latest releases are deployed to NPM

Local Usage (Developer contributions welcome)

  1. Install MetaMask Flask https://chrome.google.com/webstore/detail/metamask-flask-developmen/ljfoeinjpaedjfecbmggjgodbgkmjkjk
  2. Setup wallet
  3. Install Snap - Run yarn start in the root directory
  4. Follow install process at http://localhost:8000
  5. Installation complete! You may now go test transactions on OpenSea, Uniswap, etc.

Features

⚡️Transaction insights

Get advanced insights on your transactions, including built-in security measures. Our transaction insights are powered by the same security engine that keeps our 100,000+ Chrome Extension users safe!

Note- At this time signatures are not yet supported by MetaMask Snaps, only transactions. We will add this feature immediately once it is supported!

✅ Automated security notifications

Get notifications about revoking your assets, directly in MetaMask. This feature is optional.

Automated approval revoking is setup from dashboard.walletguard.app by connecting your wallet or inputting your wallet address, no signature necessary.

Audit

The snap package has been audited by Consensys Diligence.

You can view the full audit report findings here.

Permissions

This Snap requires several permissions in order to access the necessary APIs for functionality. To view the entire list of permissions, view the manifest.json.

Testing

Usage

Tests are run against the Snap build located in the dist/ folder. To run the tests follow these instructions:

  1. yarn build:clean
  2. yarn test
  3. (optional) yarn test:coverage

The project must be re-built in order re-test changes of the Snap build.

Description

  1. Unit tests: Tests of individual components and their input/outputs (e.g- RevertComponent.test.ts)
  2. Integration Tests: Testing the end-to-end integrations and external dependencies. For example the Wallet Guard transaction simulation API and it's responses are mocked out in index.test.ts. Assertions are made on the outcome and sum of the components, rather than logic within those components.

Dev Standards / Best Practices

Components

UI elements must be organized by components. Ideally we should unit test the component itself along with the e2e functionality where that component is being used.

Components must have the name Component in the filename and function name for clarity. Components should be functions so that we have the option to pass in parameters.

Well-tested code

This project uses the Metamask Snaps Testing SDK and Jest for testing. We also use SonarCloud to manage code coverage and quality. (60% minimum on PRs)

Right the Metamask Snaps Testing SDK does not include code coverage for certain files/APIs such as index.ts but we have made sure to build strong test cases here.