That's how it should work, but now how it actually works. From https://github.com/ampproject/amphtml/issues/534#issuecomment-273273590 https://github.com/amppro

That's how it should work, but now how it actually works. From https://github.com/ampproject/amphtml/issues/534#issuecomment-273273590 https://github.com/ampproject/amphtml/issues/534#issuecommen...: > "AMP is an evergreen JavaScript library. We will not allow users to lock themselves into a particular release." Which completely precludes using SRI. Further, pages serving their own copy of the JavaScript "won't be considered valid AMP," and thus would be ineligible for the placement benefits afforded to AMP pages in Google results. AMP's governance is not similar to HTML's. Changes to HTML require consensus between mutually competing browsers, while AMP is a single-vendor land-grab. That consolidation of power threatens to return us to the dark ages of Microsoft's sole dominance of the de facto Web.