You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
• Replaces MIT licensing with CC BY-NC-SA 4.0 for code and documentation.
• Adds full license terms, copyright notices, and commercial licensing guidance.
• Aligns package metadata and README references with the new terms.
The following are alternative approaches to this PR:
1. Use a software-specific license
➕ Can address source code distribution and modification more explicitly
➕ May better align with established software licensing practices
➖ Requires selecting or drafting terms matching the intended noncommercial restrictions
➖ May not preserve the exact Creative Commons attribution and ShareAlike model
2. Keep one canonical full license copy
➕ Avoids duplicating hundreds of lines across LICENSE and LICENSE.md
➕ Reduces the risk of future legal-text drift
➖ The Markdown license page would no longer be fully self-contained
➖ Consumers may need to follow a link to read the complete terms
Recommendation: Confirm that applying CC BY-NC-SA 4.0 to software is the intended legal strategy, since Creative Commons generally recommends software-specific licenses for code. If retained, use LICENSE as the canonical full text and keep LICENSE.md focused on the summary, API terms, and a link to that canonical copy.
Files changed (4) +899 / -23
Documentation (3) +898 / -22
LICENSEReplace the MIT template with CC BY-NC-SA 4.0 terms+445/-2
Replace the MIT template with CC BY-NC-SA 4.0 terms
• Adds 2025 and 2026 copyright notices and the complete CC BY-NC-SA 4.0 International license text for the package code and documentation.
LICENSE.mdDocument noncommercial repository and API licensing+450/-18
Document noncommercial repository and API licensing
• Replaces the MIT terms with CC BY-NC-SA 4.0, adds commercial licensing contact guidance, corrects the generated-data license name, and embeds the full license text.
1. Readers miss author attribution✓ Resolved🐞 Bug≡ Correctness
Description
LICENSE adds the 2026 CyteTypeR authors as copyright holders, while the README-linked LICENSE.md
still identifies only Nygen Analytics AB. Because both files present themselves as the repository
license and the README routes users to the incomplete one, recipients receive inconsistent
attribution information.
The package metadata selects LICENSE as its license file, and that file names both Nygen Analytics
AB and the 2026 CyteTypeR authors. The human-facing license document names only Nygen Analytics AB,
while the README directs users to that incomplete document.
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
## Issue description
The canonical `LICENSE` names the 2026 CyteTypeR authors as copyright holders, but the README-linked `LICENSE.md` omits them, creating inconsistent attribution information.
## Fix Focus Areas
- LICENSE[1-6]
- LICENSE.md[3-9]
- README.md[147-150]
## Recommended Fix
Add the 2026 CyteTypeR authors copyright notice to `LICENSE.md` so it matches the canonical `LICENSE` file.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Context sources
Review mode: ⚖️ Balanced: This is a licensing and package metadata contract change with potentially significant legal and distribution implications, so it warrants a careful single-pass review.
Tip of the day
💡 Did you know, you can route each action level your way: inline, summary, both, or drop
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated license to CC BY-NC-SA 4.0.