[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-open-source-license-risk-zh-CN":3,"blog-adjacent-open-source-license-risk-zh-CN":29,"blog-related-open-source-license-risk-zh-CN":61},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":28},119,"open-source-license-risk","开源协议风险：企业在用，但并不了解","几乎每个项目都会用到开源组件，但很少有人说得清它们的协议义务。","\u003Cp>我们评审过一些企业的项目，抽查依赖清单发现：有企业在商业产品里用了 GPL 协议的组件，还有企业使用的开源库已经三年没有维护。开源节省了开发成本，也带来了被忽视的义务。\u003C\u002Fp>\n\u003Ch2>常见的几类风险\u003C\u002Fh2>\n\u003Cp>传染性协议。GPL\u002FAGPL 类协议要求衍生作品也以相同协议开源，用在闭源商业产品里可能构成违约。\u003C\u002Fp>\n\u003Cp>维护停滞。依赖的库长期无人维护，安全漏洞不再修复，升级路径断裂。\u003C\u002Fp>\n\u003Cp>来源不明。从论坛或网盘下载的代码片段，没有明确授权信息，风险无法评估。\u003C\u002Fp>\n\u003Ch2>能做的几件事\u003C\u002Fh2>\n\u003Cp>建立依赖清单，扫描工具自动生成，每次发版更新，标注每个依赖的协议类型。\u003C\u002Fp>\n\u003Cp>明确红线：AGPL 组件不得进入核心业务代码；不明确授权的代码一律不用。\u003C\u002Fp>\n\u003Cp>对关键依赖做年检：近期提交频率、已知漏洞、是否有可替代方案。\u003C\u002Fp>\n\u003Cp>开源不是免费午餐，而是有条件的共享。把协议义务当成合同条款对待，用起来才踏实。\u003C\u002Fp>","","cyan","佳益方圆团队","2026-05-30T12:23:00+08:00",1,false,[16,17,18],"行业观察","开源","合规",{"id":20,"parentId":21,"slug":22,"name":16,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":21},5,0,"industry-watch","对互联网、软件与数字化行业趋势的深度分析，输出团队自己的判断。","globe","blue","article",20,{},{"previous":30,"next":47},{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":35,"updatedAt":35,"readingMinutes":13,"featured":14,"tags":36,"category":40},100,"facilitating-retrospectives","复盘会的主持技巧","一次好的复盘会，主持人说得少，问题问得准。","2026-06-01T12:23:00+08:00",[37,38,39],"团队文化","复盘","会议",{"id":41,"parentId":21,"slug":42,"name":43,"description":44,"icon":45,"cover":9,"tone":25,"kind":26,"sortOrder":46,"count":21},4,"team-culture","团队动态","公司活动、技术分享、团建与招聘文化，了解佳益方圆团队的日常。","users",30,{"id":48,"slug":49,"title":50,"excerpt":51,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":52,"updatedAt":52,"readingMinutes":13,"featured":14,"tags":53,"category":54},21,"seven-years-what-changed","七年，我们改变了什么","从三个人到二十人，从什么单都接到知道自己擅长什么，变化比想象中慢，也比想象中扎实。","2026-05-28T12:23:00+08:00",[],{"id":55,"parentId":21,"slug":56,"name":57,"description":58,"icon":59,"cover":9,"tone":25,"kind":26,"sortOrder":60,"count":21},6,"founder-notes","创业手记","创始团队在经营、管理与产品上的思考，记录一家软件公司的成长过程。","pen-tool",10,[62,73,83],{"id":63,"slug":64,"title":65,"excerpt":66,"content":9,"cover":9,"tone":67,"author":11,"publishedAt":68,"updatedAt":68,"readingMinutes":13,"featured":14,"tags":69,"category":72},108,"gansu-manufacturing-digitalization","甘肃制造业数字化的三个观察","跑了十几家本地制造企业之后，我们看到数字化不再是买软件，而是补基础。","slate","2026-10-09T09:00:00+08:00",[16,70,71],"制造业","数字化",{"id":20,"parentId":21,"slug":22,"name":16,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":21},{"id":74,"slug":75,"title":76,"excerpt":77,"content":9,"cover":9,"tone":25,"author":11,"publishedAt":78,"updatedAt":78,"readingMinutes":13,"featured":14,"tags":79,"category":82},109,"local-software-budget","本地软件预算的两个新趋势","预算总额没有明显增长，但花钱的方式变了：更少的一次性大项目，更多的持续性投入。","2026-09-27T10:13:00+08:00",[16,80,81],"预算","信息化",{"id":20,"parentId":21,"slug":22,"name":16,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":21},{"id":41,"slug":84,"title":85,"excerpt":86,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":87,"updatedAt":88,"readingMinutes":13,"featured":14,"tags":89,"category":92},"cross-border-first-90-days","品牌出海的前 90 天：独立站、支付与履约","有一个英文网站只是开始。真正决定出海成败的，是站点之外的支付、合规与交付体验。","2026-09-18T10:30:00+08:00","2026-10-18T15:58:14.692+08:00",[90,91],"品牌出海","跨境电商",{"id":20,"parentId":21,"slug":22,"name":16,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":21}]