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

pocketuniverse

v0.0.15

Published

A transaction checker that helps you avoid crypto scams.

Downloads

9

Readme

PocketUniverse

Known Vulnerabilities

Layout

Injected

The injected script proxies requests from the website to PocketUniverse before forwarding it to window.ethereum.

We don't modify the request but rather just wait until the user decides it wants to continue.

We communicate our requests with the content-script through the DOM.

ContentScript

This is responsible for communicating with the webpage. It takes the webpage request and stores it in local storage for the service worker to pick it up.

Background

This service worker handles the requests and popup triggering logic.

It listens to changes in storage and forwards requests if there are new things to simulate.

Popup

This is what the user sees when there is a simulation in progress. This simply uses the storage state to be displayed.

It will write to storage the action the user decides to take.

Contributions

If you'd like to contribute, feel free to pop in the discord or DM us on twitter. I'd be happy to chat :D

Contact Us