Consider migrating from abandoned `license-checker` to `license-checker-evergreen`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 25.9k
- Forks
- 2.4k
- Avg merge
- 13h 10m
- Merged PRs (30d)
- 4
Description
Summary
I noticed this project uses license-checker for license auditing. The original package hasn't been updated since January 2019 (over 6 years!) and appears to be abandoned.
Suggested Alternative
license-checker-evergreen is an actively maintained fork with several improvements:
- Full TypeScript support with included type definitions
- ES Modules native support (not just CommonJS)
- Node.js 18+ optimized for current LTS versions
- Additional output formats: Markdown, Tree view, Plain Vertical
- Active maintenance with regular security updates
- Drop-in replacement - same CLI flags, same output formats
Migration (30 seconds)
npm uninstall license-checker
npm install license-checker-evergreen
# Update scripts: license-checker → license-checker-evergreen
Drop-in replacement - same CLI flags, same output formats.
Why This Matters
Using an unmaintained package for license compliance creates risk:
- No security patches for 6+ years
- No support for newer Node.js versions
- No bug fixes or improvements
Happy to answer any questions about the migration!
Disclosure: I maintain license-checker-evergreen
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the npm dependency and scripts that reference license-checker. Compare the proposed package's compatibility with the current audit commands, then replace the references and run the project's license-auditing workflow to confirm it still works with the same flags and output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- security, tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100