[{"data":1,"prerenderedAt":35},["ShallowReactive",2],{"web":3},[4],{"createDate":5,"articleThumb":6,"tagIds":7,"categoryId":9,"articleId":10,"isTop":11,"excerpt":12,"readingTime":22,"wordCount":23,"categoryInfo":24,"tagInfo":28,"id":33,"title":34},"2026-08-25 15:59:25","https:\u002F\u002Fcdn.jfork.top\u002Fimages\u002F20260825111119031.webp",[8],12,10,"web-crypto-api",false,{"type":13,"value":14},"minimark",[15,19],[16,17,18],"p",{},"在过去很长一段时间里，只要一提到在前端进行加密、解密、生成哈希（MD5\u002FSHA）或生成随机数，绝大多数开发者的第一反应就是 npm install crypto-js。作为曾经的功勋库，crypto-js 陪伴我们度过了无数个项目。",[16,20,21],{},"然而，随着 Web 标准的演进，现代浏览器早已内置了一个更强大、更安全、性能也更恐怖的官方武器——Web Crypto API。时至今日，如果你还在新项目里打包第三方的加密库，是时候了解一下为什么要换成原生 API 了。",33.5,6031,{"name":25,"symbol":26,"icon":27,"id":9},"Node.js","node","i-anyfork-node",[29],{"name":30,"symbol":31,"icon":32,"id":8},"浏览器","web","i-anyfork-website","blog\u002Fblog\u002F9.Web Crypto API浏览器原生加密的终极指南.md","Web Crypto API 浏览器原生加密的终极指南",1791553131038]