Removing Google's binary blobs is mitigating one issue, but replacing it with an entire binary blog from an anonymous github user might be introducing new ones.
On that note - can you tell us more about the project? ie. if you plan on keeping this updated long terms (i've watched a lot of promising chromium forks fade after an initial big splash), what your plans are, if you'll you accept contributions, how the binary distributions are built so we can verify the checksums, if you can tag the Chromium releases from Google so they can be verified, etc.
I've had the idea of a chromium fork with privacy enhancements in the back of my mind for a while now (turns out a lot of people have) specifically to replace Tor Browser and/or have a lighter browser (without canvas, webgl, webrtc etc.) with better defaults (ie. no hardware access, location, notifications, cookies, history, etc.) for opening links, private browsing etc[1].
This may be a good base to work on - assuming you want to go beyond just "de-googlify"
[1] I think there is a real need for an alternate browser that is lightweight[2] and has stricter privacy and security controls - with proper user segregation (ie. you really don't want to open random links from social media in the same browser session as where you're logging into your primary accounts).
[2] ie. do to Chrome/Firefox what Firefox originally did to Netscape - and Chrome would be the better foundation to work on