Almost every item on this marketplace ships third-party code inside it. A CSS framework, a charting library, an icon set. You are selling that code onward, and not every licence lets you.
The ones that are fine
MIT, Apache 2.0, BSD and ISC all permit redistribution inside a commercial product. Keep the original licence text in your package, usually in a licences folder, and you have met the obligation. This covers the large majority of what you will want to use.
The one that catches people
GPL, and its stricter relatives. If you bundle GPL code, the licence's position is that your work becomes subject to the same terms, which is incompatible with selling a licence that forbids redistribution. LGPL is more forgiving when the library is linked rather than copied in, but "linked" means something specific and it is worth reading rather than assuming.
Fonts and icons are code too
An icon set licensed for personal use cannot ship in something you sell, however small. Commercial font licences frequently exclude redistribution entirely, meaning you may use the font on your own site but not hand it to every buyer. This is one of the most common reasons an item is pulled after it has already sold.
Images are the sharpest edge
A stock photo licence almost never allows redistribution inside a product. If your demo content includes photographs, either license them for that use explicitly or ship placeholders and let the buyer supply their own.
What to actually do
- Keep a list of every dependency and its licence, updated as you add them
- Ship the licence texts with your package
- Where a licence requires attribution, put it somewhere a buyer will not delete by accident
An item pulled for a licensing problem takes its sales with it, and the buyers keep their licences to something you can no longer support.
