Skip to content
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

False 'bugs' verification #22

Open
Paul-Reed opened this issue Feb 18, 2022 · 2 comments
Open

False 'bugs' verification #22

Paul-Reed opened this issue Feb 18, 2022 · 2 comments

Comments

@Paul-Reed
Copy link

Authors appear to be able to 'mislead' the scorecard by providing a generic 'git' url in the package.json such as;

"bugs": {
"url": "https://github.com/paul-reed/node-red-contrib-mynode"
},

Instead of the 'bug's' url - https://github.com/paul-reed/node-red-contrib-mynode/issues
But then disabling issues in the git rep settings, so bugs cannot be reported, but gains a point in the scorecard...

I assume that there is access to the url in the package.json, if so, couldn't a regex determine if the url was suffixed with /issues (or the equivalent gitlab etc suffix).
Taking it a step further, maybe a further check could determine in the url actually existed.

Example - https://github.com/Supergiovane/node-red-contrib-tts-ultimate

@Paul-Reed
Copy link
Author

PR #23 adds further verification checks.

@hardillb
Copy link
Member

Just to add to this, on GitHub, if issues are dissabled the link 302 rediects to /pulls which would be a useful test

e.g. https://github.com/d0uub/node-red-contrib-puppeteer-new/issues -> https://github.com/d0uub/node-red-contrib-puppeteer-new/pulls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants