Tampermonkey is not Open Source

Just letting you know
Reading time: about 1 minute

This post is meant to be a short remark about something I noticed today. It is about Tampermonkey, a browser extension for managing User scripts.

Tampermonkey, like Greasemonkey, lets you create and run User scripts. These are small JavaScript snippets that can execute on any URL you want. You can consider them mini-extensions.

Tampermonkey came out as a Greasemonkey alternative for Chrome. Since writing User scripts is a “developer” thing to do, and since pretty much all software development tools are open source, so was Tampermonkey. This quickly allowed them to gather a user base and get contributions from the community.

At some point (around version 2.9), they switched their project to a proprietary license. They stopped taking contributions of course, and the old version is still on GitHub, so there is no license violation. This post isn’t meant to be a “grab your pitchforks there’s proprietary software” post against Tampermonkey either. I just know that some people don’t want to run non-free software, and their browser might’ve auto-updated to a non-free version.

This was certainly the case for me. I remembered Tampermonkey as an open-source user script manager and started using it, it took me a while to realize the license situation. While this information was available on the Firefox add-ons page, I think it should be more prominent in the install process.

After some time, and with developments like major browsers all implementing the same extension API, Tampermonkey took its place on most Add-On stores. I believe for Firefox at least this was after the license change, so people on FF shouldn’t have had unexpected non-free software.

Tampermonkey alternatives

The most well-known alternative on Firefox is Greasemonkey. You can get Greasemonkey here.

A more cross-platform option might be Violentmonkey. It works on Chrome, Firefox, and many other browsers.

The following pages link here

Citation

If you find this work useful, please cite it as:
@article{yaltirakli201909tampermonkeyclosedsource,
  title   = "Tampermonkey is not Open Source",
  author  = "Yaltirakli, Gokberk",
  journal = "gkbrk.com",
  year    = "2019",
  url     = "https://www.gkbrk.com/2019/09/tampermonkey-closed-source/"
}
Not using BibTeX? Click here for more citation styles.
IEEE Citation
Gokberk Yaltirakli, "Tampermonkey is not Open Source", September, 2019. [Online]. Available: https://www.gkbrk.com/2019/09/tampermonkey-closed-source/. [Accessed Oct. 10, 2024].
APA Style
Yaltirakli, G. (2019, September 05). Tampermonkey is not Open Source. https://www.gkbrk.com/2019/09/tampermonkey-closed-source/
Bluebook Style
Gokberk Yaltirakli, Tampermonkey is not Open Source, GKBRK.COM (Sep. 05, 2019), https://www.gkbrk.com/2019/09/tampermonkey-closed-source/

Comments

Comment by josephcsible
2022-02-12 at 07:53
Spam probability: 0.368%

> They stopped taking contributions of course, and the old version is still on GitHub, so there is no license violation. Wait, wasn't Tampermonkey's old license GPL, with no CLA? So isn't the copyright of all previous contributors being violated?

Comment by Guest
2019-09-05 at 09:42
Spam probability: 2.146%

https://violentmonkey.github.io/ works the same and is MIT licence.

Comment by Robert Headley
2019-09-05 at 09:38
Spam probability: 2.296%

I started using Violent Monkey around that time. https://violentmonkey.github.io/ It is better anyway. :P

© 2024 Gokberk Yaltirakli