Privacy choices

Git-Stars uses essential storage for site operation. Optional analytics stays disabled unless you accept it. This choice does not enable advertising. Privacy Policy

LogoGit-Stars
Top StarsTrendingAI AgentsPicksViral ReposInsightsTools
LogoGit-Stars

Discover top GitHub projects with real rankings and AI insights

AboutLogo of Git-StarsGit-Stars
Rankings
  • Top Stars
  • Trending
  • AI Agents
  • Picks
  • Explore
Resources
  • Insights
  • Tools
  • Editorial Policy
About
  • About
  • Contact
Legal
  • Privacy Policy
  • Terms of Service
© 2026 Git-Stars. All Rights Reserved.
← All tools
Git-Stars · Practical tools

License scenario checklist

Separate commercial use, distribution and network-service questions. Get checks, not legal clearance.

Your use scenario

What to check

General information, not legal advice or commercial approval. Verify the repository’s actual license first. Summaries are not authoritative license text.

Answer the questions to see relevant checks. Unknown conditions are not treated as absent obligations.

How to use the result

Verify the repository's exact release and license identifier before using the worksheet. Choose whether you modified the covered program, conveyed copies, enabled network interaction or added separately licensed assets. The result selects issues to inspect, not a legal verdict. Unknown answers and unsupported or multiple licenses remain manual-review cases. Original license text governs; summaries and translations are only aids. Sources checked October 16, 2026.

A worked example

For a modified AGPLv3 program that supports remote user interaction, select AGPL-3.0-only, modification yes and network service yes. The source-offer check appears. Do not generalize that result to all website code, an unmodified program, or GPLv3 with no copies conveyed. What counts as modification, covered work or conveying can require legal review of the actual architecture.

What this cannot establish

Commercial activity, distributing a closed-source derivative and selling hosted access are different questions. This tool cannot determine license compatibility, derivative-work boundaries, contractual exceptions, patent exposure or model/data rights. A checklist with no unanswered questions is still not approval. If you selected the wrong version or omitted a distributed component, the result can be inapplicable. No license is not assumed to mean permission.

Sources and further reading

  • MIT original text ↗
  • Apache-2.0 original text ↗
  • GNU GPLv3 original text ↗
  • GNU AGPLv3 original text ↗
  • Docling: code and model licenses are separate →

Git-Stars Editorial · Independent tools; not affiliated with the projects mentioned. Editorial policy