Open Source Licenses
Transparent. Compliant. Community‑driven.
VideoFlow is built with respect for open source. We proudly disclose our dependencies and the licenses that govern them.
- Currently no external open‑source dependencies
- Future components will be clearly listed with licenses
- We honor MIT, Apache 2.0, BSD, and other permissive licenses
- Full attribution will be provided when required
1. Introduction
VideoFlow – Privacy-First Universal Video Speed Controller is developed by Ahmad Free Tools. We believe in the power of open source software and the collaborative spirit behind it. This page exists to provide complete transparency about the open source components used within the extension, the licenses that govern them, and how we ensure compliance.
While the VideoFlow extension itself is not open source (it remains a proprietary, free‑to‑use tool), we may incorporate open source libraries to enhance functionality. We are committed to respecting the hard work of open source developers by adhering to their license terms and providing proper attribution.
2. Our Open Source Philosophy
Ahmad Free Tools stands on the shoulders of the open source community. We recognize that without freely available, well‑maintained libraries, modern software development would be impossible. We strive to:
- Give credit – every author and contributor deserves acknowledgment.
- Comply fully – we read and respect the terms of every license we encounter.
- Keep records – any library we use is documented here, including its exact license text.
- Contribute back – when possible, we share improvements or bug fixes with the upstream projects.
Transparency is key. If you have questions about any dependency or license, please reach out – we’re happy to discuss.
3. Current Dependencies
At present, the VideoFlow extension is written entirely in vanilla JavaScript and has zero external open source dependencies. It does not bundle or dynamically load any third‑party libraries, npm packages, or CDN resources.
This deliberate simplicity ensures a minimal attack surface, faster performance, and complete control over the codebase. All functionality – from UI to playback rate manipulation – is implemented from scratch by Ahmad Free Tools.
4. Future Dependencies
We may, in the future, decide to incorporate open source libraries to add features or improve development efficiency. Any such library will be carefully vetted for security, license compatibility, and community trustworthiness. If and when we add dependencies, this page will be updated to include:
- The exact name and version of the library.
- A direct link to its source repository.
- The full text of the applicable open source license.
- Any required copyright notices or attribution.
We will never introduce a dependency that would compromise our privacy‑first architecture (e.g., libraries with tracking, telemetry, or non‑permissive licenses that could restrict user freedoms).
5. Common Open Source License Types
For users curious about what different open source licenses mean, here is a brief overview of the most common categories we may encounter:
- Permissive licenses (MIT, Apache 2.0, BSD) – allow reuse with minimal restrictions, typically requiring only that the original copyright notice and license text be included.
- Copyleft licenses (GPL, AGPL) – require that derivative works also be distributed under the same license, ensuring the code remains open.
- Weak copyleft (LGPL, MPL) – permit linking with proprietary code under certain conditions, while modifications to the library itself must remain open.
VideoFlow, being a browser extension distributed as a compiled package, would primarily interact with permissive licenses. We will clearly explain any license obligations as they arise.
6. MIT License
The MIT License is one of the most popular and permissive open source licenses. It allows anyone to freely use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software, provided that the original copyright notice and permission notice are included in all copies or substantial portions of the software.
If we ever incorporate an MIT‑licensed library, you will find the complete license text and copyright attribution listed in the “Third‑Party Notices” section below. We fully comply with the MIT requirement to reproduce the copyright notice and disclaimer.
7. Apache License 2.0
The Apache License 2.0 is a permissive license similar to MIT, but with additional protections around patent rights and a more detailed termination clause. It explicitly grants patent rights from contributors to users, and requires that any modified files carry prominent notices stating that changes have been made.
Should VideoFlow use an Apache‑licensed component, we will include the required NOTICE file (if provided) and the full license text. We respect the Apache requirement to not use the project’s name for endorsement without permission.
8. BSD License
BSD licenses (2‑Clause, 3‑Clause) are permissive and short. They generally require that redistributions of source code retain the copyright notice, list of conditions, and disclaimer. The 3‑Clause version adds a non‑endorsement clause preventing the use of the project’s name to promote derivative products without permission.
If a BSD‑licensed component becomes part of VideoFlow, we will ensure that the appropriate copyright notice and disclaimers are included in our documentation or within the extension’s assets.
9. GPL (General Public License) Considerations
The GPL family (GPLv2, GPLv3, AGPL) is a strong copyleft license. If VideoFlow were to incorporate GPL‑licensed code, the entire extension might need to be released under the GPL as well – a decision we would make very carefully. Because VideoFlow is a browser extension, linking with a GPL library could have implications for how we distribute the combined work.
Current stance: We avoid GPL‑licensed dependencies to maintain the freedom to license VideoFlow as we see fit while still respecting the community. If we ever include GPL code, we will clearly state the specific license version and how users can obtain the corresponding source code.
10. Attribution Requirements
Proper attribution is not just a legal requirement; it’s a sign of respect for the developers who build the tools we rely on. For any open source component used, VideoFlow will:
- Reproduce the original copyright notice.
- Include the full license text (or a link to it).
- Indicate if any modifications were made.
- Place this information in an accessible location – either within the extension’s options page, in a LICENSE file inside the package, or on this web page.
If you notice any missing attribution, please contact us immediately – we will correct it.
11. Third‑Party Notices
This section is reserved for the specific third‑party notices and license texts of any open source components we incorporate.
Currently empty. As noted, VideoFlow has no external dependencies. When we add any, they will be listed here with the exact license wording and copyright attributions.
We encourage you to bookmark this page if you are interested in tracking future changes.
12. Contact Information
For questions regarding our use of open source, compliance, or to suggest an open source component we should consider, please reach out:
- Contact Page: https://videospeed.ahmadfreetools.com/contact-us/
- Extension Homepage: https://videospeed.ahmadfreetools.com/
- Developer: Ahmad Free Tools
- Email Support: support@ahmadfreetools.com
Open source thrives on communication. We’re just an email away.
Frequently Asked Questions
Is VideoFlow itself open source?
Currently, no. VideoFlow is a free‑to‑use proprietary extension. However, we may release certain non‑core components under open source licenses in the future. Our code is visible to anyone via Chrome’s developer tools, but redistribution and modification rights are limited by our Acceptable Use Policy.
Why doesn’t VideoFlow use any open source libraries?
Simplicity and privacy. By writing everything ourselves, we eliminate supply‑chain risks and keep the extension lightweight. It also ensures that we never accidentally introduce a license that conflicts with our goals.
If you add a library, how will I know?
This page will be updated immediately. Additionally, the Chrome Web Store listing’s “Developer” section may mention the use of open source components, and a new section may appear within the extension’s own UI (like an “About” or “Credits” area).
Do you accept contributions from the community?
We are not currently accepting code contributions, but we love feedback and suggestions. If you have an idea for a feature or a library you’d like us to consider, please contact us.
Will you ever release VideoFlow as fully open source?
It’s possible. As the project matures, we may choose to open‑source the entire extension under a permissive license like MIT. We’ll announce it clearly if that happens.