License Finder FAQs

Question 1

When should I use this skill?

Accepted Answer

You should use this skill whenever you are adding new dependencies to a project, performing a legal compliance audit, or evaluating whether a library's license is compatible with your project's redistribution requirements.

Question 2

What happens if a license cannot be found in PyPI metadata?

Accepted Answer

If PyPI metadata is missing or incomplete, the skill automatically initiates a 'fallback' mode. It identifies the source repository URL and uses a shallow clone to search for physical license files (like LICENSE, COPYING, or README) to ensure deterministic results.

Question 3

Does it support specific package versions?

Accepted Answer

Yes, the skill supports version-specific analysis. This is crucial for historical accuracy, as a package's license may change between different releases.

Question 4

What does the License Finder skill do?

Accepted Answer

The License Finder skill automates the discovery of Python package licenses. It uses a deterministic two-step process: first querying PyPI metadata, and if unsuccessful, performing a shallow Git clone to scan the source repository for license, copying, or copyright files.

Question 5

How does this skill improve my development workflow?

Accepted Answer

It eliminates the manual effort of hunting for license files across different platforms. By integrating directly into your Claude Code environment, it provides instant, accurate legal information without requiring you to leave your terminal or IDE.

License Finder

License Finder

Características Principales

Casos de Uso

Características Principales

Casos de Uso