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

attribution-artisan

v0.1.2

Published

Generate THIRD_PARTY_NOTICES.md and JSON from installed dependencies. Zero-dep CLI + GitHub Action.

Readme

Attribution Artisan

Zero‑dep CLI + GitHub Action that generates THIRD_PARTY_NOTICES.md from your installed dependencies and (optionally) embeds license texts for MIT/BSD, etc. Pairs perfectly with License Lens.

build release npm License: MIT Ko-fi


Table of contents


Overview

Attribution Artisan walks node_modules/ (including nested deps), collects each dependency’s name@version, license, and homepage/repository, then writes a clean THIRD_PARTY_NOTICES.md. You control whether to embed full license texts for select SPDX identifiers (e.g., MIT, BSD-2-Clause, BSD-3-Clause).

  • Zero dependencies; Node ≥ 18
  • No registry calls — reads local package.json and license files
  • Optional JSON output for auditing
  • Works with npm, pnpm, yarn

Quick start

# ensure you have node_modules (in CI: npm ci / pnpm i / yarn install)
npx attribution-artisan generate

Create a config for policy:

cat > attribution-artisan.config.json <<'JSON'
{
  "includeTexts": ["MIT","BSD-2-Clause","BSD-3-Clause"],
  "exclude": ["@types/*"],
  "sort": "name"   // or "license"
}
JSON

# generate
npx attribution-artisan generate

Usage

# Markdown (default: THIRD_PARTY_NOTICES.md)
npx attribution-artisan generate

# JSON only
npx attribution-artisan generate --format json

# both Markdown + JSON
npx attribution-artisan generate --format both

# custom output file
npx attribution-artisan generate --out NOTICE.md

# override includeTexts via CLI
npx attribution-artisan generate --include-texts MIT,BSD-3-Clause

Exit codes

  • 0 — success
  • 2 — runtime error (e.g., no node_modules/)

Configuration

Create attribution-artisan.config.json at repo root (all optional):

{
  "includeTexts": ["MIT","BSD-2-Clause","BSD-3-Clause"],
  "exclude": ["@types/*"],
  "sort": "name"
}
  • includeTexts — SPDX ids whose license texts should be embedded (if found in the package or templates).
  • exclude — glob patterns on package name to skip (supports * and scopes like @types/*).
  • sortname (default) or license.

Output format

Markdown (THIRD_PARTY_NOTICES.md)

  • Intro block with timestamp & policy
  • Per‑license sections: packages listed as - name@version — homepage/repo
  • Optional appended license texts for includeTexts

JSON (third_party_notices.json)

{
  "generatedAt": "2025-08-14T12:00:00.000Z",
  "packages": [
    { "name": "left-pad", "version": "1.3.0", "license": "MIT", "homepage": "https://...", "repository": "https://..." }
  ],
  "embeddedTexts": { "MIT": "..." }
}

CI (GitHub Actions)

Minimal check

name: attribution-artisan
on: [push, pull_request]
jobs:
  generate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: 20 }
      - run: npm ci
      - run: npx attribution-artisan generate

Composite Action usage (after you publish)

- uses: hunt3r157/attribution-artisan@v1

Notes & limitations

  • Reads installed package metadata. Ensure node_modules/ exists first.
  • License detection:
    • package.json.license (string or { type: "..." }), else licenses[]
    • Falls back to UNKNOWN if absent
    • For embedded texts: Artisan searches package license files (LICENSE, COPYING, etc.) then uses simple built‑in templates for common SPDX ids.

Security

No telemetry, no network calls, local file reads only.


Contributing

PRs welcome! Keep runtime dependency‑free. Add new SPDX templates under templates/licenses/ when useful.


License

MIT © Attribution Artisan contributors


Roadmap

  • [ ] More SPDX templates
  • [ ] HTML export
  • [ ] Support non-Node ecosystems via manifest inputs
  • [ ] Option to inline license snippets per package

FAQ

Why not parse lockfiles?
License fields aren’t in lockfiles. Installed package metadata is the most accurate without network calls.

Will it support monorepos/workspaces?
Yes. It follows nested node_modules/ directories and scopes (e.g., @scope/*).

Can I exclude dev dependencies?
First release lists everything installed. We can add --prod-only in future releases if needed.