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

fs-lock

v1.2.0

Published

open_basedir and file_accessdir for Node

Downloads

712

Readme

fs-lock - open_basedir and file_accessdir support

This module implements open_basedir and file_accessdir inside of Node.js.

  • open_basedir: Validates that all require's are inside these directories.
  • file_accessdir: fs module methods are verified against these directories.

If a path is not validated, it will throw an error (either throw or err out the callback).

Usage

The goal for this module is to help when you are loading 3rd party modules and you need to restrict their access. A few examples of this come to mind:

  • CLI apps that work only in a certain dir and load 3rd party add-ons.
  • Running a Node.js server process and you rely on 3rd party code to read things from the fs
  • You are paranoid and want to make sure someone doesn't touch what they shouldn't

When you use this module, you require it and configure it in your controlled script. Then any call/require after that will be forced to use these predefined scoped directories.

Notes

Since this is written purely in Javascript, there are likely places that a user could override other methods to gain access. I have tried to prevent this with Object.freeze on the two Object's that are modified so that they can't be modified again.

Overrides

The constructor to fs-lock can not be called more than once, this means that once the settings are in place, they can not be overrided (except for testing, view code to see that).

The only overrides available for this are a set of Environment variables that are read at init time. Environment vars where chosen because if you have access to them you probably have access to the script too.

  • NODEJS_FILE_ACCESSDIR
  • NODEJS_OPEN_BASEDIR

Both of these support the standard : separator and will be auto processed when the module is loaded.

Example

//Do your startup code here, then lock it down with:
require('fs-lock')({
    'file_accessdir': [ __dirname, '/tmp' ],
    'open_basedir': [ '/usr/local/share/node_modules', __dirname ]
});


var fs = require('fs');

fs.readFile('/etc/passwd', function(err, data) {
    //this will throw an Access Denied error
});

Build Status

Build Status

Node Badge

NPM