diff --git a/.github/workflows/nodejs.yml b/.github/workflows/nodejs.yml
index 1b245b5..2070106 100644
--- a/.github/workflows/nodejs.yml
+++ b/.github/workflows/nodejs.yml
@@ -1,4 +1,4 @@
-name: Node.js CI
+name: packwatch CI
 
 on: [push]
 
diff --git a/README.md b/README.md
index 4eff806..7ec5de2 100644
--- a/README.md
+++ b/README.md
@@ -2,6 +2,10 @@
 
 > It ain't easy being tiny.
 
+[![codecov](https://codecov.io/gh/mcataford/packwatch/branch/master/graph/badge.svg)](https://codecov.io/gh/mcataford/packwatch)
+![packwatch CI](https://github.com/mcataford/packwatch/workflows/packwatch%20CI/badge.svg)
+[![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release)
+
 ## Overview
 
 `packwatch` is inspired by what projects like [`bundlewatch`](https://github.com/bundlewatch/bundlewatch) do for webpack bundle size monitoring and applies the same general idea to monitor your node packages' tarball sizes across time and help avoid incremental bloat. Keeping your applications as trim as possible is important to provide better experiences to users and to avoid wasting system resources, and being cognizant of the footprint of the packages you put out there is paramount.