First of all, you might want to consider two different kind of repositories :
- Those which host codes / plugins / modules for specific applications and/or Frameworks
- And those which host either generalistic portions of code or generalistic libraries.
In the second category, the first idea that comes to mind would be pear.php.net -- but there is a lot of old code, many less-than-well documented libraries, lots of not-maintained stuff, ... Which pretty much means you'll have to go through a lot of stuff and eliminate the bad libraries yourself :-(
Two possible solutions might become interesting -- and they are quite recent :
I've never used those -- but it seems like some kind of repositories anyone can upload packages to ; and those packages can then be installed using the standard PEAR installer.
There doesn't seem to be any kind of voting / reputation / whatever system associated with those, though :-( But it might be interesting to suggest that as a possible improvement ;-)
So, not a real / great answer to your question, actually : there are components and stuff out there -- but the best way to know if something is great is to either test and/or review... And some stuff just lack documentation :-(
In the first category, things might be a bit easier : for lots of frameworks / applications, there are repositories of contributed modules or classes.
For instance, for Zend Framework, this could be interesting : ZF snippets (not that much life there either, though...) ; but note that official components of the framework are generally much more useful/better.
And that is probably true for many frameworks out there...
Another example would be Drupal and it's repository of modules -- and, there, you have some sorting by usage possibility, which is a bit of an indication of the quality (generally speaking) of those modules.