Open-source licencesIT Law

Open-source licence guide and third-party notices file for your software

Usually ready in 15 minutesRevisions includedQuality check
Packages
Payment protectionDetails
  • Revisions within the package are free.
  • If you do not respond within 3 days of delivery, the work is accepted automatically.

The money is reserved when you pay and released only once you accept the work.

Open-source licence guide and third-party notices file for your software

Example result

Example for the Standard package

Open-source licence and notices file: a desktop app for photographers

Licence options for the SDK

LicenceWhat it allowsFits?
MITAnyone can use it, even in closed products, if they keep the noticeYes: the simplest for plugin authors
Apache 2.0Like MIT, plus an explicit patent grantYes, if patents matter to you
GPL 3.0Plugins built on it must also be open sourceNo: it would put off commercial plugin authors

Recommendation: MIT.

Dependency check (excerpt)

PackageLicenceWhat you must do
LibRawLGPL 2.1Link dynamically, ship the licence text, let users replace the library
sharpApache 2.0Include the licence and its NOTICE
exif-readerMITKeep the copyright line
FFmpeg buildLGPL 2.1Build without the --enable-gpl flag

THIRD-PARTY-NOTICES.txt (excerpt)

This software includes the following third-party components.

sharp 0.33.5 — Copyright 2013 Lovell Fuller and contributors. Licensed under the Apache License, Version 2.0.

LibRaw 0.21.2 — Copyright 2008-2024 LibRaw LLC. Licensed under the GNU Lesser General Public License, version 2.1.

Notes

  • 2 of the 38 packages had no licence file at all; we listed them for the developers to replace or ask the authors
  • A practical guide, not legal advice; the FFmpeg build flags should be confirmed by whoever builds it

Client: Lumora, a two-person studio selling a photo-sorting app for Mac and Windows, with 38 open-source dependencies Task: choose a licence for the plugin SDK they want to publish, and prepare a third-party notices file for the paid app

The client and all details are made up.

About this service

Choosing between MIT, Apache 2.0, GPL or a source-available licence decides what others may do with your code, and every library you ship carries its own licence with notice duties. Tell us how you want your project used and paste or attach your dependency list with their licences, and we explain the options for your own code in plain words and build a third-party notices file in the format most licences ask for. We also flag dependency licences that may clash with how you distribute, such as copyleft code inside a closed app.

What is included

  • What you getA licence guide for your project, a third-party notices file with each component, its version, licence and copyright line, and a list of possible conflicts, as text and a Word (.docx) file. It is information, not legal advice: have a lawyer check licensing decisions that matter for your business.
  • Licence optionsPermissive, copyleft and others compared
  • Recommendation logicWhich fits the use you describe
  • Notices fileComponent, version, licence, copyright
  • Conflict flagsLicences that clash with your distribution
  • README wordingA short licence section to paste

How it works

  1. 1
    BriefYou describe the project and dependencies
  2. 2
    ReviewWe compare licences and check the list
  3. 3
    DeliveryYou get the guide and notices file

What we need from you

What the software is and how you distribute it (open repo, app store, SaaS, embedded device), what you want others to be allowed to do, and the dependency list with names, versions and licences, for example a licence report from your package manager pasted as text or attached as Word, Excel or PDF.

We will ask you:

  • How do you distribute the software?
  • What should others be allowed to do with your code?
  • Do you have a dependency list with licences?
  • Do you plan to accept outside contributions?

Compare packages

PackagesBasic$15Standard$35Premium$69
What is includedNotices fileGuide and noticesFull licensing pack
Deadline1 day2 days3 days
Revisions123
Dependencies in notices fileup to 30up to 100up to 250
Licence options compared3 optionsup to 5 optionsup to 5 options
Contributor termsNoNoYes
Order BasicOrder StandardOrder Premium

Payment protection

You pay when you order, but the money is released only for accepted work.

  • Fixed priceThe package price does not change after you pay.
  • The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
  • Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
  • Free revisionsAsk for changes within your brief as many times as the package allows.
  • Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
  • Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
How it works →

Questions and answers

Is this legal advice?

No. It explains common licences and how they usually work. Licensing can affect your business and investors, so have a lawyer confirm important choices.

Will you scan my code for licences?

No, we do not access your repository. We work from the dependency list you send; your package manager or a licence tool can produce one.

What if a licence in my list is missing or unclear?

We list it separately with what to check, such as the project's own licence file, instead of guessing.

Did not find your answer?

Packages