Maintainers of existing websites
For identifying libraries, versions and files already referenced by a page and preparing a migration inventory.
Prioritize replacement of critical production dependencies and keep verified local copies.www.bootcdn.cn · China
A free public CDN for open-source front-end libraries, with versioned files and a catalog API. Production integrations require careful attention to supply-chain integrity.
BootCDN is a public distribution service for open-source front-end libraries, launched in 2013. Its website describes joint support and maintenance with Bootstrap Chinese Network and synchronization of libraries from cdnjs. The current site footer names 佛山市铂特优选科技有限公司. The project launch date is separate from the registration date of that company.
The service centers on listed public libraries. Each library retains its upstream license. Hosting business files, customer-domain configuration, bandwidth contracts and credit-backed availability commitments require separate arrangements.
The public JSON API provides library summaries, names, versions and file lists for dependency inventories and asset catalogs. Its documentation describes synchronization as usually daily; compare individual versions with upstream releases.
Security research published on September 5, 2026 documented conditional poisoning of the tldjs 2.3.1 file on cdn.bootcdn.net: selected responses appended a malicious loader to the original library. The report concerns specific files, responses and dates; it does not establish that every library file is malicious on every request.
Browsers execute third-party scripts, so free access and HTTPS do not replace content integrity and trust in the distributor. Direct references are currently not recommended for new production dependencies. Existing sites should inventory references, obtain and verify dependencies from trusted upstream sources, and prefer self-hosting or a distributor with a clear trust boundary. For external scripts, combine pinned versions with SRI hashes obtained from a trusted source.
For identifying libraries, versions and files already referenced by a page and preparing a migration inventory.
Prioritize replacement of critical production dependencies and keep verified local copies.For reviewing library file structures and versions when updating references in examples.
Choose a suitable delivery source and recheck licensing and compatibility before using an example in production.For using public metadata to assist with library, version and file inventories.
Check API transport security and freshness; rely on trusted upstream releases for version and integrity decisions.Prefer trustworthy resource sources for new production work. For existing BootCDN references, pin versions, verify upstream files and plan migration, using SRI and cross-origin attributes where applicable.
Explore products by use case: what they do, how to use them and whether they are billed separately.
Provides HTTPS URLs organized by library version and file path. Library pages support version selection, file filtering and copying a URL or script/link markup. These listings can help inventory existing dependencies; verify the selected files, licenses and compatibility against their upstream projects.
Provides library summaries and names, plus version and file lists for individual projects. Current HTTPS API requests redirect to HTTP, so integrations must check the complete transport path. Cache metadata and verify it against trusted upstream sources; it should not be the sole basis for automatic production updates.
Sites referencing included front-end libraries and their public versioned files
Free
BootCDN provides free public distribution of open-source libraries. Its website does not list paid user plans, traffic unit prices or overage fees. Free access does not establish a contractual promise of unlimited usage or perpetual availability.
Its public catalog and free distribution make historical library files easy to locate, but documented conditional poisoning of specific resources creates a significant supply-chain trust concern. Existing integrations should prioritize a dependency inventory, verification and migration.
For production references, assess script privileges, trusted upstream sources, pinned versions and SRI. A single clean response does not establish catalog-wide safety, and catalog metadata does not replace integrity checks on delivered files.
Explore BootCDN products, use cases and buying advice