README.md

CDNJS - the best front-end resource CDN for free!

Table of Contents

Introduction

This is the main repository to maintain the libraries' assets on CDNJS. For website and API, please refer to new-website repository, all the repositories can be found at CDNJS organization on GitHub!

CDNJS is a free and open source project to organize all the famous web front-end development resources and provide them to the developers with faster CDN infrastructure without usage limitation and fee. We want to help individual library/framework developers spread their projects, and help web developers to supercharge their websites! With the great and free CDN service, developers can focus on the project and website development, without spending time worrying about how to setup a CDN for the project or website assets. We hope to make web development easier, your websites and the WWW faster and safer.

If you love 💖 what we are doing and would like to help us make the project better, please consider to:

Currently, CDNJS is the top 2(ref) web front-end CDN service with great performance. We fully support https, SPDY, http/2.0 and SRI, which will boost and secure your website with zero configuration. (note that you'll still need to take care of the server side and application layer of security issues. We make it better, but can't help too much if you implement a bad practice)

latest version url support

Note that we don't support the feature to use latest in the url, because of the reasons below:

It brings potential risks to break the website if there is any compatible issue or bug coming from upstream. It's not a good idea to use it in the production environment, both jQuery CDN and Google CDN don't provide this feature.

The latest url feature also has cache and performance issues, which has conflicts of what we are tring to do - make your website load as fast as possible.

Security issues become more and more important nowadays, for example, GitHub had been attacked by the Great Cannon via malicious JavaScript(ref1, ref2) during April 2015, one of the techniques to prevent this kind of attack is Subresource Integrity(SRI). We have been supporting this feature for a long time, but the latest url feature totally conflicts with the SRI technique.

Contributing

To contribute to CDNJS, please refer to the CONTRIBUTING.md, it should contain most of the things you'll need to get your contribution started!