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

filesystemlinter

v0.0.1-1

Published

Linter for project's file system

Readme

filesystemlint

Linter for project's file system

Why?

Linter would be useful for whom, who have multirepo projects, CI and don't want to care about file structure on code-review. Additionally linter would be helpful for new developers in project.

API

CLI

fslint --target="." --config="./.fslintrc"

Node.js

const fslint = require('filesystemlint')

fslint({
    configPath: './.fslintrc',
    target: '.',
    ignore: ['node_modules', '.git', '.idea']
})

Recommended config

There

Rules

  • cases - files' and folders' case
  • crlf (not developed) - new line cr/lf chars
  • max-depth - max depth of folder/file in project
  • new-line-end-file - \n in end of each file
  • no-dirs-extension - folders without extensions
  • no-duplicates - same name files and folders with different extensions
  • no-empty-dirs - folder without children
  • no-empty-files - file with zero size
  • project-structure (not developed) - json-schema project sctucture (need to be /lib folder, optional Jenkinsfile, etc.)
  • required-index - in each folder must be index file
  • ...your recommendations

Coming features

  • Reading of plugins
  • Reading of extends
  • Fix flag
  • Quiet flag
  • File reporters
  • Throwing errors
  • Global ignore patters (some folder are hardcoded for the current moment)
  • Personal rule ignore patters
  • Structure comparing
  • Stream, links and other
  • ...your recommendations

Credentials