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
In order to improve license detection, it is imperative that we find a package's GitHub repository, since there's a very high change the license is going to be declared there.
We must parse github.com and github.io homepages, infering the repository url from these urls:
Here's an example. This Node.js package declares the homepage as:
"homepage": "http://zaach.github.com/jsonlint/"
We can safely infer the associated GitHub repository, which is http://github.com/zaach/jsonlint. Inside this repository, the license can be inferred from parsing the README.md file, using the method described in #10.
This is very easy to do, as it is just a matter of adding another regular expression inside app/github/repository.py.
The text was updated successfully, but these errors were encountered:
In order to improve license detection, it is imperative that we find a package's GitHub repository, since there's a very high change the license is going to be declared there.
We must parse github.com and github.io homepages, infering the repository url from these urls:
Here's an example. This Node.js package declares the homepage as:
We can safely infer the associated GitHub repository, which is http://github.com/zaach/jsonlint. Inside this repository, the license can be inferred from parsing the
README.md
file, using the method described in #10.This is very easy to do, as it is just a matter of adding another regular expression inside
app/github/repository.py
.The text was updated successfully, but these errors were encountered: