-
Notifications
You must be signed in to change notification settings - Fork 508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can I contribute to "Repo lookup from PyPI too conservative to use" #3249
Comments
I think 1 could work, or a modified version of 2. :
happy to help review |
@spencerschrock Local commit is ready for review. Can you provide me access to make a PR here?
Also I'm not familiar with Gitlab URLs but if you have some examples I'm happy to add them to this PR |
You're trying to push your branch to our repo. You'll need to push the branch to your fork, and send the PR from the fork (relevant doc links: fork and PR). |
Describe the bug
Many PyPI packages specify their GitHub source repository in ways that
scorecard
cannot parse. The issue seems to be that PyPI places no restriction on the names in theproject_urls
map. scorecard however only looks at exactly one key and then bails if it doesn't find a github repo there.Consider the structure of these very well supported projects, which all use different structures
Reproduction steps
scorecard --pypi numpy # This fails
Expected behavior
I think
scorecard
ought to be able to handle this non-uniformity to find a github repo.Additional context
I'm happy to put in a PR to fix this (already started) if the reviewers agree with the approach (and will help me with my golang =D).
Proposal 1: Construct and ordered list of case & whitespace insensitive keys to check in project urls. If any look like a github repo use the first one that matches.
Proposal 2: Find all the github repos listed in project_urls. Fail if there are any number of repos besides exactly 1 found.
Thank you so much for this tool!
The text was updated successfully, but these errors were encountered: