Skip to content

Update LICENSE.md #3340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RobbieTheWagner merged 1 commit into from
Jan 29, 2026
Merged

Update LICENSE.md #3340

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
73 changes: 53 additions & 20 deletions LICENSE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,23 +1,56 @@
# License

We added a commercial license to be able to provide better support and features
for Shepherd users. If you are using Shepherd for a commercial project, you will
need to obtain a commercial license at
[shepherdjs.dev](http://shepherdjs.dev/pricing).

However, if you are using a Shepherd version **older than v14.0.0**, you don't
need to obtain a commercial license.

### Commercial license

If you want to use Shepherd for a commercial application, theme or plugin the
commercial license is the appropriate license. With this option, your source
code is kept proprietary. Purchase a commercial license at
[shepherdjs.dev](http://shepherdjs.dev/pricing)

### Open-source license

Copyright (c) 2024 Ship Shape Consulting, LLC
# Shepherd.js License

Shepherd.js is dual-licensed under **AGPL-3.0** (for open source and non-commercial use) and a **Commercial License** (for commercial use).

---
🆓 Free Use - AGPL-3.0 License
You may use Shepherd.js **FREE OF CHARGE** under the AGPL-3.0 license if you are:
✅ Open Source Projects
- Your project is open source and licensed under an AGPL-compatible license (GPL, AGPL, etc.)
- Your complete source code is publicly available
✅ Personal & Non-Commercial Use
- Personal projects, portfolios, and hobby websites
- Educational purposes (students, teachers, coursework)
- Academic research projects
✅ Evaluation & Testing
- Evaluating Shepherd.js for up to 30 days
- Development, testing, and staging environments during evaluation
- Proof-of-concept and demo projects
Comment on lines +15 to +18
Copy link

@coderabbitai coderabbitai bot Jan 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

git ls-files LICENSE.md

Repository: shipshapecode/shepherd

Length of output: 76

🏁 Script executed:

cat -n LICENSE.md | head -30

Repository: shipshapecode/shepherd

Length of output: 1808

🏁 Script executed:

wc -l LICENSE.md

Repository: shipshapecode/shepherd

Length of output: 80

🏁 Script executed:

tail -n +30 LICENSE.md | head -50

Repository: shipshapecode/shepherd

Length of output: 2509

Clarify the 30-day evaluation period in the Evaluation & Testing section.

The "up to 30 days" evaluation clause lacks essential details that could enable unintended loopholes: it doesn't specify whether this is a one-time period per organization, repeatable per evaluation attempt, or defined by consecutive calendar days versus actual usage days. Without explicit scope boundaries, organizations could repeatedly claim evaluation status. Add specific language such as "a one-time 30-day evaluation period per organization" or "30 consecutive calendar days from first use" to prevent disputes.

🤖 Prompt for AI Agents 
In `@LICENSE.md` around lines 15 - 18, Update the "Evaluation & Testing" clause
under the "Evaluation & Testing" heading: replace the ambiguous phrase
"Evaluating Shepherd.js for up to 30 days" with explicit language such as "a
one-time 30 consecutive calendar day evaluation period per organization,
commencing on first use" (or alternate approved wording) and add a short
sentence clarifying it cannot be repeated or reset; ensure the new text appears
alongside the existing bullet points about development, testing, and
proof-of-concept use so the scope is unambiguous.

**Important:** If you use Shepherd.js under AGPL-3.0, you must:
- Make your complete source code available if you distribute or provide your software over a network
- License your code under AGPL-3.0 or a compatible license
- Comply with all AGPL-3.0 terms (see full license text below)
---
💳 Commercial License Required
You **must purchase a commercial license** at [shepherdjs.dev/pricing](https://shepherdjs.dev/pricing) if:
❌ Commercial Products & Services
- You're building a commercial product, application, SaaS, or website that generates revenue
- Your company generates revenue (even if the specific project using Shepherd.js does not)
- You're using Shepherd.js in any customer-facing commercial application
❌ Closed-Source Use
- You cannot or don't want to open-source your code under AGPL-3.0
- You want to keep your source code proprietary
- You want to avoid AGPL's source code disclosure requirements
❌ White-Label, Resale, or OEM Use
- You're embedding Shepherd.js in a product you sell or distribute
- You're offering Shepherd.js as part of a commercial service or hosting
- You're using Shepherd.js in a product sold to other businesses
❌ Internal Business Tools
- You're using Shepherd.js for internal tools, dashboards, or admin panels in a revenue-generating company
- Even if the tool is not customer-facing, commercial licenses are required for for-profit companies
**Why Commercial License?**
- ✅ No AGPL obligations - keep your code proprietary
- ✅ Legal protection and indemnification
- ✅ Priority support and updates
- ✅ Lifetime license with no recurring fees
[**Purchase Commercial License →**](https://shepherdjs.dev/pricing)
---
❓ Still Not Sure?
If you're unsure whether you need a commercial license:
- **Contact us:** [ahoy@shipshape.io](mailto:ahoy@shipshape.io)
- **View pricing:** [shepherdjs.dev/pricing](https://shepherdjs.dev/pricing)
**When in doubt:** If your organization generates revenue, you likely need a commercial license.
---

### GNU AFFERO GENERAL PUBLIC LICENSE

Expand Down