docs: fix badges in readme

Author: faceyspacey

README.md

@@ -17,43 +17,10 @@
   </a>
 
   <a href="https://gitter.im/extract-css-chunks">
-    <img src="https://img.shields.io/gitter/room/nwjs/nw.js.svg" alt="Downloads" />
+    <img src="https://img.shields.io/gitter/room/nwjs/nw.js.svg" alt="Gitter Chat" />
   </a>
 </p>
 
-<p align="center">
-  <a href="https://www.npmjs.com/package/travis-github-status">
-    <img src="https://img.shields.io/npm/v/travis-github-status.svg" alt="Version" />
-  </a>
-
-  <a href="https://travis-ci.org/faceyspacey/travis-github-status">
-    <img src="https://travis-ci.org/faceyspacey/travis-github-status.svg?branch=master" alt="Build Status" />
-  </a>
-
-  <a href="https://lima.codeclimate.com/github/faceyspacey/travis-github-status/coverage">
-    <img src="https://lima.codeclimate.com/github/faceyspacey/travis-github-status/badges/coverage.svg" alt="Coverage Status"/>
-  </a>
-
-  <a href="https://greenkeeper.io">
-    <img src="https://badges.greenkeeper.io/faceyspacey/travis-github-status.svg" alt="Green Keeper" />
-  </a>
-
-  <a href="https://lima.codeclimate.com/github/faceyspacey/travis-github-status">
-    <img src="https://lima.codeclimate.com/github/faceyspacey/travis-github-status/badges/gpa.svg" alt="GPA" />
-  </a>
-
-  <a href="https://www.npmjs.com/package/travis-github-status">
-    <img src="https://img.shields.io/npm/dt/travis-github-status.svg" alt="Downloads" />
-  </a>
-  
-  <a href="https://snyk.io/test/github/faceyspacey/travis-github-status">
-    <img src="https://snyk.io/test/github/faceyspacey/travis-github-status/badge.svg" alt="Known Vulnerabilities" data-canonical-src="https://snyk.io/test/github/faceyspacey/travis-github-status">
-  </a>
-
-  <a href="https://www.npmjs.com/package/travis-github-status">
-    <img src="https://img.shields.io/npm/l/travis-github-status.svg" alt="License" />
-  </a>
-</p>
 
 Like `extract-text-webpack-plugin`, but creates multiple css files (one per chunk). Then, as part of server side rendering, you can deliver just the css chunks needed by the current request. The result is the most minimal CSS initially served compared to emerging JS-in-CSS solutions.