Information and Roadmap

j•ko was born out of the need to organize and share scripts and dependencies between projects—a gap that, after some research, I found was left for external tools by the npm team about 10 years ago, rather than being integrated directly into package.json (I believe a solution like allowing a package.js, as eslint does, would have been preferable). As development progressed, it evolved into a tool for automating tasks as well. I hope it proves to be highly useful for everyone.

Licenses

jko executable can be used in personal or commercial projects for free. This documentation content is licensed under CC BY-SA 4.0.

jko Executable and Source code

Executable Software License (ESL)

Permission is hereby granted, free of charge, to any person obtaining a copy of this executable software (the "Software") for use, testing, evaluation, and distribution—including for commercial purposes—subject to the following terms and conditions:

Executable-Only Distribution: The Software is provided solely in executable (binary) form. The corresponding source code is not provided under this license.
Modification and Derivative Works: Users are not permitted to modify, reverse-engineer, decompile, or create derivative works of the Software in any form. The Software must be used exactly as distributed.
Redistribution: Redistribution of the original executable must include a copy of this license in its entirety and must retain all copyright and licensing notices contained herein. Any redistribution must clearly state that it is the original unmodified version of the Software.
Attribution: The name(s) of the original author(s) shall not be used to endorse or promote any redistributed version of the Software without prior written permission from the author(s).
Future Licensing Changes: This license covers only the distribution of the Software in its current executable form. The author reserves the right to change the licensing terms in future releases, including the option to publish the source code under a different license.

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 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.

jko Documentation (this documentation)

Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0)

You are free to share and adapt it, provided you give appropriate credit and distribute any derivative works under the same license.

🔧 Maintenance Plan

I am committed to the continued growth and evolution of this project. Currently, this project is distributed as an executable under a custom license that restricts modifications and reverse-engineering. However, I recognize the value of open collaboration and the benefits of a more permissive licensing model.

Maintenance and Bug Fixes: Right now, my main focus is on keeping the executable stable and addressing any bugs that arise, along with continuously updating and improving the documentation so that everyone has a clear understanding of how to use the project. I’m holding off on rolling out major new features or enhancements until the project transitions to an open-source model—where I look forward to welcoming contributions and fresh ideas from the community.

Looking Ahead: With the support I receive—whether through donations, sponsorships, or community contributions—I plan to transition to a more permissive license, such as the MIT License or GNU General Public License, and release the source code. This support primarily covers the initial effort and time I invested in bringing this wonderful project to life. This change will allow free and open modification of the software and make it easier for anyone to contribute ideas, improvements, and innovations.

I remain dedicated to transparency and will keep you updated as my plans evolve. The timing and specifics of this transition may change depending on future legal, financial, and developmental considerations.

🤝 Support

Your donations, sponsorships, and community contributions help keep this project running and evolving, while also supporting a transition to a more permissive license. I welcome both one-time donations or recurring sponsorships.

Donate

📝 Feedback

Your feedback is invaluable. It helps me identify gaps and areas that need simplification. I continuously refine the documentation to ensure it remains effective and user-friendly, and the executable benefits from ongoing, community-driven improvements.

Licenses​

🔧 Maintenance Plan​

🤝 Support​

📝 Feedback​

Licenses

🔧 Maintenance Plan

🤝 Support

📝 Feedback