Is AGPL-3.0 compatible with ISC?
Yes.
Combined work becomes AGPL; network use triggers source disclosure.
Result license is the more restrictive of the inputs. You must satisfy every input license's notice and source-offer terms. Verify pairwise compatibility first.
Resulting work's license: AGPL-3.0-only
General guidance, not legal advice.
Obligations when redistributing as open source
- AGPL-3.0: retain the copyright notice and license text.
- AGPL-3.0: state significant changes made to the code.
- AGPL-3.0: provide complete corresponding source of the combined work.
- AGPL-3.0: the combined distributed work must be licensed under AGPL-3.0-only.
- ISC: retain the copyright notice and license text.
Other distribution models
These licenses sit the same way against each other under every distribution model, but the model decides whether you can ship the result. Not possible under:
- Proprietary software you distribute as a binary — AGPL-3.0 requires the entire distributed work to be licensed AGPL-3.0-only with complete corresponding source, so a proprietary binary is not possible. Distribute the whole work under AGPL-3.0-only, or replace the AGPL-3.0 component.
Check this pair in the tool to switch models.