The MongoDB Database
SSPL 1.0
SSPL-1.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
The source is published, but the license restricts what you may do with it. This is not open source, and the restriction is usually aimed squarely at commercial use.
- ScanCode classifies this as "Source-available" — published source under terms that are not open source. Treat approval as a policy question, not a formality.
You can
- Read the source, and generally use it internally or for development and testing
- Modify it for uses the license actually permits
You must
- Read the specific restriction before you build on it — competing-service clauses (SSPL), change dates (BUSL), and non-commercial limits all behave differently
- Check your company's policy: most treat these as blocked by default
You cannot
- Assume OSI-style freedoms — offering it as a service, or shipping it commercially, is what these licenses exist to prevent
- Treat it as interchangeable with the permissive license the project may have used previously
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 — SSPL-1.0 (100% of the reference text)
Reporight matched the file against the ScanCode LicenseDB reference text for SSPL-1.0.
- 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.