Announcement: The Upcoming Version 2.0 Will Be Released Under Dual-License: AGPLv3 License / UAParser.js "PRO" License
Hi All, We've been announcing this change in a discussion page two weeks ago, but since it might not reach the large part of the community, we will provide more details about the change here: > TL;DR all the past and future releases of version `0.7.x` / `1.0.x` remain MIT, while version `2.0.x` will be under AGPL. ## What the license change means Starting from version 2.0 you'll be able to choose between using our regular free & open-source license (under AGPLv3) or PRO license. [AGPLv3](https://opensource.org/license/agpl-v3/) is an OSI-approved open-source license from GNU, pretty much same as GPL, only with an addition of network clause. If you opt for the free version of UAParser.js, you just need to provide the source and changes that you've made to the library. If you opt for the PRO License instead, you don't have to open-source your modifications. We offer 3 tiers of PRO License: Personal (non-commercial), Business (1 license per project), and Enterprise (indefinite projects). Note that if you are using the current stable version of `v0.7.x` / `v1.0.x` then you __won't__ be affected by this change since this new license will __only__ applies to `v2.0.x` upwards. You can continue using those old versions as usual without the need to revisit the terms as we have no plan to re-license them. The development for those versions also won't get prioritized, alhough they might still get occassional updates, particularly for bugfix-related updates. ## Behind the change L
Posted by faisalman on Oct 9, 2023, 4:22 AM
Tags
Related issues
- [UPDATE NOW] PHP RCE Vulnerability (CVE-2026-109618 and CVE-2026-109619)
- Server requests and latency increased after upgrading from Next.js 15 to 16
- Leak of Geedge Networks internal documents (100,000+ from Jira, Confluence, GitLab)
- Can't download videos from YouTube on cobalt.tools
- `google_service_networking_connection` produce an error when trying to destroy the resource
- WebGPU-based renderer for the editor
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (Network)
[UPDATE NOW] PHP RCE Vulnerability (CVE-2026-109618 and CVE-2026-109619)
Server requests and latency increased after upgrading from Next.js 15 to 16
Leak of Geedge Networks internal documents (100,000+ from Jira, Confluence, GitLab)
Can't download videos from YouTube on cobalt.tools
`google_service_networking_connection` produce an error when trying to destroy the resource
WebGPU-based renderer for the editor
Zed downloads NodeJS binary and npm packages from Internet without user’s consent
FR: Allow custom domains for Tailscale Funnel
Announcement: The Upcoming Version 2.0 Will Be Released Under Dual-License: AGPLv3 License / UAParser.js "PRO" License
Hi All, We've been announcing this change in a discussion page two weeks ago, but since it might not reach the large part of the community, we will provide more details about the change here: > TL;DR all the past and future releases of version `0.7.x` / `1.0.x` remain MIT, while version `2.0.x` will be under AGPL. ## What the license change means Starting from version 2.0 you'll be able to choose between using our regular free & open-source license (under AGPLv3) or PRO license. [AGPLv3](https://opensource.org/license/agpl-v3/) is an OSI-approved open-source license from GNU, pretty much same as GPL, only with an addition of network clause. If you opt for the free version of UAParser.js, you just need to provide the source and changes that you've made to the library. If you opt for the PRO License instead, you don't have to open-source your modifications. We offer 3 tiers of PRO License: Personal (non-commercial), Business (1 license per project), and Enterprise (indefinite projects). Note that if you are using the current stable version of `v0.7.x` / `v1.0.x` then you __won't__ be affected by this change since this new license will __only__ applies to `v2.0.x` upwards. You can continue using those old versions as usual without the need to revisit the terms as we have no plan to re-license them. The development for those versions also won't get prioritized, alhough they might still get occassional updates, particularly for bugfix-related updates. ## Behind the change L
Comments (0)
No comments yet. Start the discussion.