License changes
Packages and modules whose license changed between versions. Older versions keep their old license; upgrading past the line is what changes your terms. Release history for PowerShell modules is under PowerShell module versions.
Filters
Saved searches 0
Keep up to eight named searches. Saved in this browser. Filters are also shareable in the page address.
No license changes recorded
The recorded package histories show no license change between adjacent versions. Collection continues in hourly batches; Sources shows what is tracked and any failures. An empty list does not establish that licenses have never changed.
How this works
Checked counts are installation totals. Download totals vary by registry; watches follow your saved choices.
Groups are review hints based on recorded source statements. They do not decide what your organisation may do. “Most restrictive” is a review order; conditions and commercial alternatives are not a universal legal ranking.
- Permissive
- Typically permits broad reuse subject to attribution and other stated obligations.
- Weak copyleft
- May require sharing changes to covered components; boundaries depend on the license.
- Copyleft or paid
- Reciprocal terms or a commercial option; inspect the actual choices.
- Conditional
- Permission depends on stated conditions and your organisation's circumstances.
- Source-available
- Source is available with restrictions on some uses.
- Non-commercial only
- Commercial permission is not established by the free terms.
- Vendor terms
- Publisher-specific terms need individual review.
- Unknown
- The collected evidence does not establish a group.
Publication dates are package dates, not the date this installation discovered a change. Histories may be incomplete; changes inside the same group are visible on the package detail page.
Information only, not legal advice. Conditions depend on your organisation and use; read the original terms.