Node.js JavaScript runtime ✨🐢🚀✨
Artistic 2.0
Artistic-2.0The license text is a full match, but GitHub would not assert a license. GitHub recognises a shorter list than ScanCode does, so this is common for newer or source-available licenses — and it can also mean the file was modified.
What this means for you
Changes to the licensed files stay open; the rest of your program usually does not have to be. Read before embedding.
You can
- Use the library in a larger work that has a different license, including a proprietary one
- Distribute the combined work commercially
You must
- Publish your changes to the licensed files under the same license
- Keep notices, and tell recipients where to get the licensed source
- Preserve the recipient's ability to relink or replace the library (LGPL)
You cannot
- Take modifications to the licensed files private
- Add restrictions that block the rights this license grants downstream
This is not legal advice. Your obligations depend on how you use the code and your jurisdiction. Consult counsel for production risk.
How we know
- exact textFull text match — Artistic-2.0 (100% of the reference text)
Reporight matched the file against the ScanCode LicenseDB reference text for Artistic-2.0. It also resembles MIT, Zlib.
- github apiGitHub declares 'Other'
GitHub found a license file but would not attribute it to a standard license — usually custom or modified text.
This summary reads the repository root only. Vendored trees and per-file headers can differ — run a deep scan to map every file.