PHP Classes

Detecting poor/bad packages

Recommend this page to a friend!

      PHP Classes blog  >  PHP Modern Practices ...  >  All threads  >  Detecting poor/bad packages  >  (Un) Subscribe thread alerts  
Subject:Detecting poor/bad packages
Summary:Github details
Author:Alan Cameron
Date:2016-11-10 15:36:48
Update:2016-11-10 19:16:00

  1. Detecting poor/bad packages   Reply   Report abuse  
Picture of Alan Cameron Alan Cameron - 2016-11-10 18:56:47
Have you any advice on checking GitHub packages for quality. I have downloaded a number some of which were empty and some incomplete. There does not appear to be any way a user can tell. Those with no updates are an obvious clue but not reliably. Those with a few updates are possibly better but again not reliably.

Should I complain to GitHub about this?

  2. Re: Detecting poor/bad packages   Reply   Report abuse  
Picture of Manuel Lemos Manuel Lemos - 2016-11-10 19:16:00 - In reply to message 1 from Alan Cameron
Quality is subjective. What is quality for some, may not be for others.

There are some tools that make some checks but those are mostly on code statistics.

Like the last updated date, the code statistics are just quality hints about the developer work.

There is not much point complaining to GitHub or PHPClasses because this is user contributed content. Sites have no power to fix the code. Also rejecting packages just because some people disagree on quality matters, may not be fair because it is subjective.

PHP Classes at least lets users rate packages on several aspects and leave comments. That is more objective but still may not be enough.

For more information send a message to info at phpclasses dot org.