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

@chiffre/push

v2.11.5

Published

Shared types for push.chiffre.io

Downloads

42

Readme

Push

Continuous Integration Coverage Status Dependabot Status

Microservice to collect encrypted analytics & process metadata.

Chiffre.io Transparency Initiative

This service is where the encrypted visitor data arrives on the Chiffre analytics platform. As we believe transparency is paramount in providing a privacy-first service, we're keeping this repository public as a "no trick up our sleeve" promise.

Here, most events are collected using two methods:

  • POST with the encrypted payload in the body
  • GET with the encrypted payload in a query string argument

The first one is preferred by the tracker script, and uses either fetch or sendBeacon, depending on context and availability.

If neither are available or fail, the tracker script falls back to an <img> tag, which uses the GET route with the payload in the query string.

Noscript

Clients without JavaScript enabled cannot generate end-to-end encrypted payloads. In order to count them in without revealing too much, we generate an encrypted message on the fly on the server on their behalf, containing only the following information:

  • Event type (session:noscript)
  • Time of the request
  • Country of origin (2-letter ISO country code, given by CloudFlare)

That's it. We explicitly do not reveal the path or user-agent, even though we technically could, as a desire to respect the visitor's privacy (we consider disabling JavaScript as the ultimate protection against tracking).