licensed

2026 · 2 min read

Simple CLI to produce license copy for README.md.

Problem

Usually a license section of a project is just "MIT" and maybe some verbiage justifying it or doubling down on it or, honestly, idk what people are doing down there in their license sections, because, like you, my eyes progress from glazing over to calcified when I start processing that section of the README. But that doesn't make it unimportant. So, I wanted a command I could just run and it barfs out what my license is and then parses my package.json for any runtime dependencies that I should mention. And I want to do this because my stuff is nearly always under the Unlicense, which makes it important, not just to highlight other OSS projects, but to acknowledge that my bullshit project stands on the lithe and somewhat sinewy shoulders of my forecoders.

Outcome

Run a command, get a markdown license section. It reads your package.json, finds your license file, and spits out formatted copy with a table of all your dependencies and their licenses. Paste it into your README and move on with your life. Forecoders acknowledged.

Domains

CLIlicensing

Tools

JavaScript (VJS)

Addendum

Also, when you dogfood as much as I do, it is genuinely hilarious to see a markdown table of 5 deps, and 3 of them are yours. Under the Unlicense. Looking at the rest of the licenses with that accusatory tone reserved for the level of disapproval that can only be matched by a mother. This will never get old.