What's the problem with third party javascript? Honestly, there's quite a few issues. Here are some of the most relevant ones:

1. You don't have control over what the 3P JS does on your site or when updates are made to it. With each 3P tag added to your site, you give the ability for someone else to push changes to your site without your knowledge or control.

2. There are lots of performance tradeoffs with adding a third party tag to your site. Over the years, the web has become flooded with 3P JS, it's quite common for there to be more 3P JS than first party. The browser has to go through a bunch of additional work for each new domain it has to download content from.

3. Are your 3P JS providers using best practices? Most people today simply trust their 3P JS is using efficient caching, minified code, and global CDNs.

We built a simple tool to help alleviate some of these pains that gives you control of your third party JS. We do this by:

1. Tagsafe captures and hosts the content of each 3P tag you specify and hosts them behind a single CDN, consolidating all of your third party JS to a single domain.

2. We then monitor the "origin" for changes. When a changes is made, we will capture a new version of that tag and host it. This gives you the ability to view the changes made by the tag provider through a git-diff like view, and rollback capabilities so that you control what version is live on your site.

3. We have a small, inlined JS snippet that you place at the top of your web pages. The JS will intercept 3P script tags added to your page and re-point them the Tagsafe CDN version.

This is an early version, and we have lots of ideas of where this could go. We'd love any thoughts, feedback, or contributions as we continue to build this out.