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 🙏

© 2026 – Pkg Stats / Ryan Hefner

arcan

v1.0.4

Published

Analyze the architecture

Readme

Arcan

Architecture Analyzer

Arcan is project architecture analyzer, it is designed to allow you to configure rules for how you want a project to be structured. Filenames, required files and directories can be configured at all levels of the project.

The goal of this project is to allow a architecture to remain consistent over time.

Usage

Arcan will by default look for arcan.config.js which is expected to be a node modules exporting a config object.


module.exports = {

    // the files property contains all normal file configurations

    files: {

        pattern: /my_file/,             // Arcan will report any files that do not match the provided pattern
        required: ['important_file']    // Arcan will report if the directory does not contain the required file

    },

    directories: {

        requireAll: {...},              // Arcan will report any subdirectory that does not follow the provided config
        foo: {                          // here we can set what subdirectories we want to configure rules for

            files: {...},
            directories: {...}

        }

    }

};

Arcan will ignore any subdirectories that do not contain any rules. All configurations are optional.