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

connect-block-hotlinks

v1.0.0

Published

Middleware for blocking cross-origin requests (hotlinks)

Downloads

6

Readme

connect-block-hotlinks

I wrote this middleware to keep people from embedding my site's images into their own sites. It compares the HTTP headers Host and Referer to make sure they are from the same 2nd-level domain. For example, if Host is img.example.com then referer can be http://example.com/ or http://blog.example.com/ but not http://another.com/.

This will not stop a determined attacker! For that you should use CORS and authentication mechanisms. But it will prevent people stealing your bandwidth by using a URL to your image in the 'src' of an tag on another site.

API

It follows a classic Connect/Express middleware pattern:

var express = require('express');
var blockHotlinks = require('connect-block-hotlinks');

var app = express();
app.use "/img/*", blockHotlinks

Depending on the request, the middleware will either:

  • do nothing, and call next() so the route can be handled by the next route handler.
  • return a 403 Forbidden "Missing 'Host' HTTP Header"
  • return a 403 Forbidden "Missing 'Referer' HTTP Header"
  • return a 200 OK hotlinking-disallowed.png