License

Published on May 10, 2026 • Last updated on May 10, 2026


ScriptLog is free software. Not "free as in free trial." Not "free with limitations." Free as in you can download it, run it, modify it, sell it, and build on top of it without paying anyone, asking anyone, or explaining yourself to anyone.

This page covers the license ScriptLog is released under, what that means for you in plain terms, and how the open source model works.

The License

ScriptLog is released under the MIT License, one of the most permissive and widely used open source licenses available.

Here is the license in full:

MIT License

Copyright (c) 2018 Scriptlog

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

What MIT Means in Plain Language

Legal text is precise but rarely readable. Here is what the MIT License actually gives you permission to do.

You can use ScriptLog for anything

Personal blog, company intranet, client project, SaaS product. The license does not restrict what you build or who it is for. There is no "non-commercial only" clause. There is no restriction by industry, use case, or audience size.

You can modify it

You are not locked into the default codebase. Change the routing system. Swap out the template engine. Strip features you do not need. Add features that do not exist yet. The source is yours to work with.

You can distribute it

You can share copies of ScriptLog, modified or unmodified, with other people. You can host it somewhere for others to download. You can include it as part of a larger software package.

You can sublicense it

You can incorporate ScriptLog into a product and release that product under a different license, including a commercial or proprietary one. This is particularly relevant if you are building a hosted service or a packaged product on top of ScriptLog.

You can sell it

You can charge money for software that includes or is built on ScriptLog. The MIT License does not prohibit commercial use of any kind.

The One Requirement

The MIT License has a single condition: the copyright notice and license text must be included in all copies or substantial portions of the software.

In practice, this means:

  • If you distribute ScriptLog's source code, with or without modifications, keep the LICENSE file intact.
  • If you redistribute a compiled or packaged version that includes a substantial portion of ScriptLog's code, include the copyright notice somewhere appropriate, such as a NOTICE file, an about page, or a licenses directory.

You do not need to credit ScriptLog on your public-facing website. You do not need to open-source your own modifications. You do not need to notify anyone. The only obligation is keeping the license text in the software itself.

What You Do Not Have to Do

Confusion around open source licensing is common. Here is what the MIT License explicitly does not require of you:

Requirement Required?
Credit ScriptLog publicly on your site No
Share your modifications with the community No
Release your plugins or themes as open source No
Ask permission before using commercially No
Pay licensing fees No
Notify the ScriptLog team of your project No

Open Source Details

ScriptLog's source code is publicly hosted on GitHub. The repository contains the full application with no proprietary modules, no locked features, and no separate "enterprise edition."

What open source means for the project:

  • Anyone can read the code, audit it for security issues, and understand exactly how it behaves.
  • Anyone can submit bug reports, propose improvements, or open pull requests.
  • The project roadmap is public. There are no hidden priorities or private feature branches.
  • Releases are tagged on GitHub with version numbers and release notes.

What open source does not mean:

Open source is not the same as accepting all contributions. The maintainers review pull requests and decide what goes into core. Not every proposed feature will be merged. If something is declined, it can still exist as a community plugin.

No Warranty

The MIT License includes a no-warranty clause, and it is worth understanding what that means.

ScriptLog is provided as-is. The project maintainers make no guarantees about fitness for a particular purpose, uninterrupted operation, or freedom from bugs. If something breaks, the responsibility for your deployment sits with you. That covers your data, your uptime, and your users.

This is standard for open source software. It is not a signal of poor quality. It is the legal reality of software distributed without a support contract. If your use case requires guaranteed SLAs or commercial support, that is something you would arrange independently.

Using ScriptLog in Commercial Projects

There is nothing to sign and no one to ask. If you are building a commercial product on top of ScriptLog:

  1. Keep the LICENSE file in your copy of the ScriptLog source.
  2. Include the copyright notice if you redistribute substantial portions of the code.
  3. Build what you want to build.

That is the entire process.

A Note on Third-Party Dependencies

ScriptLog uses third-party libraries that carry their own licenses. In most cases these are also permissive open source licenses such as MIT, BSD, and Apache 2.0, but it is your responsibility to review them if your use case requires it.

The full list of dependencies and their respective licenses can be found in the project repository.

ScriptLog - Free & Open Source PHP Blog Application