Sure. Are you on some project that will be build only making use of a few UI components? Then it’s ok. A couple more I’m more used to look at:
React.rocks "A picture is worth a thousand words"
UI Components from github.com/facebook/react/wiki
Just remember that for each different component you will have to adapt the look and feel to match your application. Not mentioning responsive design. Preferably look for the less restrictive/opinionated if you might need some “out of the box” features in the future.
Otherwise, you should consider using any bigger framework to layout your components and use other separate components when that framework doesn’t provide whatever you might need. It’s just my point of view. I’ve been using third components from here and there all the time and I’ve had the same thought when dealing with many of them… “I could have done it already.” while still fighting to get that component be what you need. Although, I tend to discover another component that does the same thing I was fighting for just 10 times better and some days after I’ve already dealt with the old one… I also have to say that many awesome components/projects are released from day to day,
I like to believe that with decoupling logic from rendering in react v0.15 some standard/automatic way to create public components that inherit the default LnF (of the application running it), will see the light.