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

eslint-plugin-yet-another-license-header

v1.0.0

Published

Yet another ESLint plugin to handle a license top-comment in your JS/TS files

Readme

eslint-plugin-yet-another-license-header

This repo contains yet another eslint plugin for handling a license header comment at the top of your JavaScript/TypeScript files.

It includes a single rule, header, that will (a) report an issue if the top comment block in a checked file does not match the configured header string (or the allowed patterns) and (b) can fix (with eslint --fix) the issue by updating or adding a top comment block.

Why?

If you run into some issue with this plugin, it is very possible that the above plugins are better battle-tested.

Compatibility

Currently this is written to support eslint@9. As well, the node versions supported (see package.json#engines) are selected to match that for eslint@9.

(I'm open to supporting earlier node versions and earlier eslint versions.)

Usage

  1. Install it.

    npm install --save-dev eslint-plugin-yet-another-license-header
  2. Add it to your ESLint config file, e.g. "eslint.config.mjs":

    import {defineConfig} from 'eslint/config';
    import headerPlugin from 'eslint-plugin-yet-another-license-header';
    
    const header = `
    /*
     * Copyright Trent Mick
     * SPDX-License-Identifier: Apache-2.0
     */
    `;
    
    export default defineConfig([
        {
            plugins: {
                'yet-another-license-header': headerPlugin,
            },
            rules: {
                'yet-another-license-header/header': [
                    'error',
                    {
                        header,
                        // Or use `headerFile` to point to the header content.
                        //      headerFile: './etc/header.txt',
    
                        // Optionally provide patterns.
                        allowedHeaderPatterns: [
                            // Allow additional copyrights after "Trent Mick".
                            /^\/\*\n \* Copyright Trent Mick(, .+)*\n \* SPDX-License-Identifier: Apache-2.0\n \*\/$/,
                        ],
                    },
                ],
                // ...
            },
        },
    ]);
  3. Lint it.

    npx eslint
  4. Fix it.

    npx eslint --fix

Configuration

The header rule is configured with a single object with the following properties:

header (string)

A string that is the default license header comment to check/add to the top of JS/TS files. Leading and trailing whitespace is removed.

One of header or headerFile must be specified.

headerFile (string)

A path to a file that contains the default license header comment. Leading and trailing whitespace is removed.

One of header or headerFile must be specified.

allowedHeaderPatterns (Array<RegExp|String>)

An optional array of allowed header patterns when checking if the lead comment block of a JS/TS file is acceptable. Note that the string from header (or headerFile) is always also used when checking an existing lead comment block. Elements of this array can be a string (checks for an exact match, after trimming) or a RegExp (tests via regexp.test(leadCommentBlock)).

[!WARNING] If you use allowedHeaderPatterns to support some variance on a default license header and something changes so that a file's header does not match, then eslint --fix will replace it with the string from header (or headerFile). This means it may delete some content you had intended to include in the license header block.