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

exports-lock

v0.1.1

Published

A library to protect integrity of packages in Node.js

Downloads

6

Readme

exports-lock

A library to protect integrity of packages in Node.js

Background

JavaScript allows very flexible coding pattern, such as dynamically changing behavior by alternating the prototype chain of constructor. However, lacking of accessing control incurs vulnerability.

Can you imagine that you can change behavior of a package which is not in your hand? Current module mechanism offers NO PROTECTION for integrity of package. People can change behavior of your package once you put it in public. You cannot promise that package behaves as exactly as document saying, if somebody alternated your implementation silently.

Due to lack of convenient access control, or developers often don't care it. We exposes our code under public domain, and incurs possible malicious attacks. Now, it's pretty clear that to protect ourself, we should protect our code from maliciously changing.

I wrote this library to simply set all method/properties of public interface to not writable and not configurable. It can prevent unwanted change to your library.

Usage

Download from npm

npm install exports-lock

Lock your public interface

// entry point
const lock = require('exports-lock')

goodFunction: () => 'good function'

module.exports = {
    goodFunction
}

lock(module.exports)

If a malicious library attempts to change your code,

// malicious library
const goodLib = require('goodLib')

goodLib.goodFunction = () => 'bad'

your code will not be affected.

// client code
const goodLib = require('goodLib')
const badLib = require('badLib')

console.log(goodLib.goodFunction()) // 'good function'