[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-chocolatey-go-package-policy-installs-en":3,"article-related-chocolatey-go-package-policy-installs-en":30,"series-tools-8f987f8b-1e3b-409d-9ca9-3f0884d5e1d9":82},{"id":4,"slug":5,"title":6,"content":7,"summary":8,"source":9,"source_url":10,"author":11,"image_url":12,"cover_image":12,"category":13,"language":14,"translated_content":11,"related_article_id":15,"keywords":16,"key_takeaways":22,"views":26,"created_at":27,"published_at":28,"topic_cluster_id":29},"8f987f8b-1e3b-409d-9ca9-3f0884d5e1d9","chocolatey-go-package-policy-installs-en","Chocolatey’s Go package turns installs into policy","\u003Cp data-speakable=\"summary\">I break down Chocolatey’s Go package page into a repeatable internal install flow.\u003C\u002Fp>\u003Cp>I've been using Chocolatey for a while, and the package page for Go kept bothering me. Not because it was broken. It was because it was trying to be too many things at once: a package listing, a community noticeboard, a livestream promo wall, and a deployment guide stuffed into the same scroll. When I wanted one thing, like “how do I get Go 1.26.4 onto managed machines without making everybody hit the public repo,” I had to dig through a lot of noise. That’s the part that feels off in a lot of package catalogs. They tell you what exists, but not what you’re actually supposed to do with it in a real environment.\u003C\u002Fp>\u003Cp>Then I read the Chocolatey community package page for \u003Ca href=\"https:\u002F\u002Fcommunity.chocolatey.org\u002Fpackages\u002Fgolang\">Go Programming Language 1.26.4\u003C\u002Fa> and the surrounding guidance more carefully, and the pattern snapped into focus. This page is not just about installing Go. It’s about how Chocolatey wants you to think about software delivery: community package for discovery, internal repo for reliability, internalization when you care about control, and scripts only after you’ve decided where the package really lives. That’s a much more useful mental model than “run choco install and hope.”\u003C\u002Fp>\u003Cp>So I’m going to decompose the page the way I wish somebody had done for me: what each piece actually means, what I’d ignore, what I’d keep, and how I’d turn it into a clean internal workflow for Go. I’ll also give you a copy-ready template at the end you can adapt for your own package process.\u003C\u002Fp>\u003Cp>Before I get into the breakdown, the source that kicked this off is the Chocolatey community package repository page for Go, plus the deployment guidance embedded on that page. The repository itself is at \u003Ca href=\"https:\u002F\u002Fcommunity.chocolatey.org\u002Fpackages\u002Fgolang\">community.chocolatey.org\u002Fpackages\u002Fgolang\u003C\u002Fa>, and Chocolatey also points you to its broader docs, including \u003Ca href=\"https:\u002F\u002Fdocs.chocolatey.org\u002Fen-us\u002Fguides\u002Forganizational-deployment\u002F\">organizational deployment guidance\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fdocs.chocolatey.org\u002Fen-us\u002Fcreate\u002Fcreate-packages\u002F\">package creation docs\u003C\u002Fa>, and the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fchocolatey\u002Fchoco\">Chocolatey CLI\u003C\u002Fa> on \u003Ca href=\"\u002Ftag\u002Fgithub\">GitHub\u003C\u002Fa>. I’m not quoting view counts or stars here because the source material didn’t give me any.\u003C\u002Fp>\u003Ch2>The page is really two products pretending to be one\u003C\u002Fh2>\u003Cblockquote>Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.\u003C\u002Fblockquote>\u003Cp>What this actually means is the page is doing double duty. On one side, it’s a package catalog entry for Go. On the other, it’s a policy surface for how Chocolatey wants you to treat community packages. That distinction matters more than it looks like it should. If you read it like a normal package page, you’ll miss the operational warning hidden in plain sight: community packages are useful, but they are not the same thing as a controlled internal artifact.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781029112225-4nik.png\" alt=\"Chocolatey’s Go package turns installs into policy\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>I ran into this exact trap years ago with package managers that made public feeds feel “good enough” for production. They are good enough, right up until you need reproducibility, auditability, or a change freeze. Then the public feed becomes the thing that makes your install story wobble. Chocolatey is being unusually honest here. It’s saying: yes, use the community repo, but don’t confuse it with a guaranteed delivery channel.\u003C\u002Fp>\u003Cp>How to apply it: treat the community package page as discovery and validation, not as your final deployment source. If you are evaluating Go 1.26.4, use the public package to inspect metadata, package behavior, and community moderation signals. If you are deploying to a fleet, move the package into your own repository or internalization flow before you call it done.\u003C\u002Fp>\u003Cp>That’s the first mental shift. The page looks like a download button. It’s really a warning label with a download button attached.\u003C\u002Fp>\u003Ch2>Moderation is the real feature, not the listing\u003C\u002Fh2>\u003Cp>The page spells out the moderation process pretty plainly: security, consistency, and quality checking; installation testing; VirusTotal scanning; and human review before sign-off. That’s the stuff I care about, because package managers love to pretend metadata is enough. It isn’t. What matters is whether somebody actually looked at the package behavior before it hit the feed.\u003C\u002Fp>\u003Cp>Chocolatey’s moderation story is one of the few parts of this page that feels operationally serious. I’m not saying it makes every package safe. It doesn’t. But it does tell me the package isn’t just a random blob uploaded by a stranger and left to rot. There is at least a review path. That’s better than a lot of ecosystems that leave you to infer trust from download counts and vibes.\u003C\u002Fp>\u003Cp>Here’s the catch, and it’s an important one: moderation is not the same thing as compatibility with your environment. A package can pass moderation and still be a bad fit for your proxy rules, software allowlists, or offline deployment strategy. That’s why I never stop at “it’s moderated.” I ask “what does it do at install time, and where does it fetch from?”\u003C\u002Fp>\u003Cp>How to apply it: when I evaluate a community package, I check three things in order. First, is it moderated? Second, does the install script pull binaries from the vendor or from Chocolatey’s own cache? Third, can I internalize it without changing the install result? If the answer to the third question is no, I treat it as a candidate, not a solution.\u003C\u002Fp>\u003Cul>\u003Cli>Use moderation as a filter, not a guarantee.\u003C\u002Fli>\u003Cli>Inspect install-time download behavior before promoting a package internally.\u003C\u002Fli>\u003Cli>Assume community packages are for discovery until you own the artifact.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Chocolatey is telling you to stop trusting public feeds in production\u003C\u002Fh2>\u003Cp>The organizational use section is the part I wish more package pages had. It says reliability cannot be guaranteed on the public repository, and that packages may need to reach out to the internet at runtime. That’s the sentence that should make every platform engineer sit up. It’s not subtle. Chocolatey is basically saying: if you care about control, don’t build production around a public dependency chain.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781029109084-yo7u.png\" alt=\"Chocolatey’s Go package turns installs into policy\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>This is where a lot of teams get sloppy. They install from a public feed during development, it works, then they copy the same command into automation and act surprised when a vendor site goes down or a firewall blocks the download URL. Been there. It’s annoying, and it’s also self-inflicted. The package manager did what it said on the tin. We just didn’t read the tin carefully enough.\u003C\u002Fp>\u003Cp>Chocolatey gives you the escape hatch right on the page: host your own packages, cache community packages, or internalize them. That’s the right move for anything you expect to survive audits, network segmentation, or offline installs. If you’re running Go installs across a team, that should be your default, not your backup plan.\u003C\u002Fp>\u003Cp>How to apply it: decide where your source of truth lives before you write the install script. If the answer is “community repo,” you’re accepting runtime internet dependence. If the answer is “internal repo,” your script should point there and nowhere else. That’s the difference between a demo and a deployment.\u003C\u002Fp>\u003Cul>\u003Cli>Public repo: good for discovery, testing, and ad hoc installs.\u003C\u002Fli>\u003Cli>Proxy repo: good when you want caching but can tolerate upstream dependency.\u003C\u002Fli>\u003Cli>Internalized package: good when you want predictable installs and fewer surprises.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>The internalization flow is the part worth copying\u003C\u002Fh2>\u003Cp>The page’s “Generate Script Builder” section is where the real instructions live. It walks you through package review, integration method, internal repository URL, environment setup, and install script generation. That sequence matters because it forces you to think in the right order. Review first. Integration method second. Repository third. Script last. That’s exactly how I want deployment work to happen.\u003C\u002Fp>\u003Cp>What this actually means is Chocolatey is not trying to give you a magical one-liner. It’s trying to force a deployment decision tree. Are you using a generic shell flow, an individual machine setup, Ansible, PowerShell DSC, or something else? Are you pointing at a proxy repository or a fully internalized feed? Are you installing Chocolatey itself from your own repo? Those are the questions that determine whether the install is maintainable.\u003C\u002Fp>\u003Cp>I’ve seen teams jump straight to the script and then spend weeks patching around the bad choice they made at the start. The script becomes a ball of duct tape. Chocolatey’s flow is better because it makes the architecture visible before the code exists. It’s boring in the best way.\u003C\u002Fp>\u003Cp>How to apply it: build your package onboarding checklist around those five steps. I’d use it for Go, but I’d also use it for Node, Python, Git, anything that gets installed on more than a few machines. The goal is not to automate faster. The goal is to automate the right dependency path once.\u003C\u002Fp>\u003Ch2>Proxy repo or internalized package, pick one with open eyes\u003C\u002Fh2>\u003Cp>Chocolatey’s page gives you two main patterns. The first is a proxy repository on Nexus, Artifactory Pro, or ProGet that points upstream to the community feed and caches packages on first access. The second is an internalized package flow where you download and store the package yourself. I like that it names the tradeoff directly. Proxy is easier. Internalized is more reliable. There’s no pretending those are the same thing.\u003C\u002Fp>\u003Cp>What this actually means is you need to decide how much upstream dependency you’re willing to keep. A proxy repo is fine when you want a quick start and can live with the first-hit fetch. Internalization is what I’d use when I’m serious about repeatable installs, especially for developer tooling like Go that tends to get installed everywhere and forgotten until it breaks.\u003C\u002Fp>\u003Cp>I’ve used proxy repos in environments where the network was mostly stable and the team wanted minimal process overhead. They’re convenient. I’ve also used internalized packages in locked-down environments where convenience mattered less than “will this still work next month.” The second option wins more often than people admit, especially once security and compliance get involved.\u003C\u002Fp>\u003Cp>How to apply it: if you’re setting up Go for a workstation fleet, ask whether you can tolerate an upstream dependency during the first install. If yes, a proxy repo may be enough. If no, internalize Go and its dependencies, then point your clients at the internal feed only. Don’t mix the two casually. That’s how people end up with half-cached, half-public, impossible-to-debug installs.\u003C\u002Fp>\u003Cp>Chocolatey also names repository servers I actually see in the wild: \u003Ca href=\"https:\u002F\u002Fwww.sonatype.com\u002Fproducts\u002Fsonatype-nexus-repository\">Nexus Repository\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.jfrog.com\u002Fartifactory\u002F\">JFrog Artifactory\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Fwww.inedo.com\u002Fproget\">ProGet\u003C\u002Fa>. That’s useful because it tells you this isn’t some toy workflow. It’s designed to fit real package infrastructure.\u003C\u002Fp>\u003Ch2>The script snippets are less about syntax and more about discipline\u003C\u002Fh2>\u003Cp>The long install examples on the page, whether for PowerShell, Ansible, or other integration methods, are doing something subtle. They’re not just showing syntax. They’re showing discipline. Set TLS 1.2. Define error handling. Point to the internal repository URL. Optionally configure credentials. Pull the Chocolatey nupkg from your own source. Then install. That sequence is the whole story.\u003C\u002Fp>\u003Cp>What this actually means is the script is a policy implementation, not just an installer. The TLS line is there because old defaults are unreliable. The error action preference is there because silent failures are useless. The repository URL is there because source control for packages matters. Those are all boring details until one of them fails at 2 a.m. and you need to know why.\u003C\u002Fp>\u003Cp>I’ve had scripts that looked elegant and failed in the dumbest ways because they assumed too much about the environment. Chocolatey’s generated examples are a good antidote to that. They force you to spell out the assumptions instead of hiding them inside a wrapper function nobody remembers six months later.\u003C\u002Fp>\u003Cp>How to apply it: copy the structure, not the exact text. Keep the guardrails. Keep the explicit repository source. Keep the fail-fast behavior. Replace the package name and version with your target app. Then test it in a clean machine, not on your already-warm dev box that has half the dependencies cached from last week.\u003C\u002Fp>\u003Ch2>The Go package is the easy part. The lifecycle is the actual job\u003C\u002Fh2>\u003Cp>Once you zoom out, the Go 1.26.4 package page is really a lifecycle management page wearing a package-name badge. Go itself is not the hard part. Installing Go is easy. Keeping Go available, trusted, and consistent across machines is the hard part. That’s why the page keeps drifting back to repository strategy, internalization, and deployment tooling. Chocolatey knows the installer is the cheap part.\u003C\u002Fp>\u003Cp>This is the piece that most package pages miss. They focus on the artifact and ignore the operating model. Chocolatey does the opposite. It assumes the artifact is just the start. The real work is deciding how it moves through your environment, how it gets updated, and what happens when the public feed changes or disappears.\u003C\u002Fp>\u003Cp>How to apply it: build a tiny lifecycle policy around each package you care about. For Go, decide who owns the version, how often you refresh it, where it lives internally, and which automation path installs it. If you do that once, the next package gets easier. If you don’t, every package becomes a one-off argument.\u003C\u002Fp>\u003Cp>And honestly, that’s the part I like about this page. It’s not trying to flatter you. It’s trying to make you do the unglamorous work that keeps installs from becoming folklore.\u003C\u002Fp>\u003Ch2>The template you can copy\u003C\u002Fh2>\u003Cpre>\u003Ccode># Chocolatey package onboarding template for Go or any tool\n\n## 1) Decide the source of truth\n- Community repo for discovery and evaluation only\n- Proxy repo if first-hit caching is acceptable\n- Internalized package if installs must work without upstream access\n\n## 2) Review the package\n- Confirm the package is moderated\n- Inspect install-time download behavior\n- Check version, dependencies, and any vendor download URLs\n- Verify licensing and redistribution constraints\n\n## 3) Pick the integration path\n- Generic shell\n- Individual machine setup\n- Ansible\n- PowerShell DSC\n- Other automation framework\n\n## 4) Set repository policy\n- Internal repository URL: https:\u002F\u002Fyour-internal-repo.example.com\u002Fapi\u002Fv2\u002F\n- Optional credentials: configure only if required\n- Ensure clients point to the internal source, not the public community feed\n\n## 5) Install Chocolatey from the internal source\n- Download the Chocolatey package from the internal repository\n- Use fail-fast error handling\n- Set TLS 1.2 or your environment’s required protocol\n\n## 6) Install the package\n- Package name: golang\n- Version: 1.26.4\n- Use the internal repository as the source\n- Test on a clean machine before rolling out broadly\n\n## 7) Operational checks\n- Confirm the package installs without public internet access\n- Confirm upgrades behave the same way\n- Confirm uninstall and reinstall paths\n- Confirm logging is sufficient for support and audit\n\n## 8) Example PowerShell shape\n$ErrorActionPreference = 'Stop'\n[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072\n$repo = 'https:\u002F\u002Fyour-internal-repo.example.com\u002Fapi\u002Fv2\u002F'\nchoco install golang --version=1.26.4 --source=$repo -y\n\n## 9) Example policy note\nThis package is approved only when sourced from the internal repository.\nCommunity repository access is allowed for review, not production deployment.\n\u003C\u002Fcode>\u003C\u002Fpre>\u003Cp>That template is intentionally plain because the point is repeatability, not cleverness. Swap in your package name, your repository URL, and your automation tool of choice. The structure should stay the same even when the tool changes.\u003C\u002Fp>\u003Cp>If I were using this for Go specifically, I’d keep the package version pinned, internalize it, and make the internal repository the only source allowed in production. Then I’d document the upgrade path separately so nobody improvises it later.\u003C\u002Fp>\u003Cp>Source attribution: I pulled this breakdown from the Chocolatey community package page for Go at \u003Ca href=\"https:\u002F\u002Fcommunity.chocolatey.org\u002Fpackages\u002Fgolang\">https:\u002F\u002Fcommunity.chocolatey.org\u002Fpackages\u002Fgolang\u003C\u002Fa>. The analysis, framing, and template here are mine; the underlying package guidance and examples belong to Chocolatey Software.\u003C\u002Fp>","I break down Chocolatey’s Go package page and show how to turn it into a repeatable internal install flow.","community.chocolatey.org","https:\u002F\u002Fcommunity.chocolatey.org\u002Fpackages\u002Fgolang",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781029112225-4nik.png","tools","en","c557ef1c-7fde-4c86-918e-4fb9680ee9df",[17,18,19,20,21],"Chocolatey","Go","package management","internalization","deployment",[23,24,25],"Treat the community package page as discovery, not production truth.","Pick proxy repo or internalized package before you write the install script.","Use Chocolatey’s packaging flow to encode policy, not just install software.",0,"2026-06-09T18:18:05.601854+00:00","2026-06-09T18:18:05.59+00:00","602b2bef-8b7a-4a27-8c90-de0a4998a1f2",{"tags":31,"relatedLang":41,"relatedPosts":45},[32,34,36,38,40],{"name":19,"slug":33},"package-management",{"name":18,"slug":35},"go",{"name":37,"slug":21},"Deployment",{"name":17,"slug":39},"chocolatey",{"name":20,"slug":20},{"id":15,"slug":42,"title":43,"language":44},"chocolatey-go-package-policy-installs-zh","Chocolatey 的 Go 安裝變成政策","zh",[46,52,58,64,70,76],{"id":47,"slug":48,"title":49,"cover_image":50,"image_url":50,"created_at":51,"category":13},"aa96e422-2b01-4480-b4ce-a646be8e0993","magenta-realtime-2-score-inside-daw-en","Magenta RealTime 2 lets you score in the DAW","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781046208039-ksdz.png","2026-06-09T23:02:56.428086+00:00",{"id":53,"slug":54,"title":55,"cover_image":56,"image_url":56,"created_at":57,"category":13},"c79bca38-50b2-4d80-9a48-7f4d1afd051a","open-source-ai-tools-beat-claude-paid-tiers-en","Open-source AI tools beat Claude’s paid tiers on value","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781045269190-a1ow.png","2026-06-09T22:47:20.7972+00:00",{"id":59,"slug":60,"title":61,"cover_image":62,"image_url":62,"created_at":63,"category":13},"fbd166b2-30ad-451c-bfa5-8f190d0c4252","500-ai-agent-projects-show-where-agents-work-now-en","500 AI agent projects show where agents work now","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781033595427-zvq5.png","2026-06-09T19:32:37.573706+00:00",{"id":65,"slug":66,"title":67,"cover_image":68,"image_url":68,"created_at":69,"category":13},"c1c49550-3032-4381-bad9-a7ef29973b4d","go-support-policy-turns-releases-into-a-checklist-en","Go support policy turns releases into a checklist","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781028203465-bas6.png","2026-06-09T18:02:50.061065+00:00",{"id":71,"slug":72,"title":73,"cover_image":74,"image_url":74,"created_at":75,"category":13},"75f55dc1-b87b-4a8a-812f-bc31ab4ae4dc","rustdesk-self-hosting-secure-remote-access-en","RustDesk self-hosting setup for secure remote access","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781017372462-mgyj.png","2026-06-09T15:02:24.622252+00:00",{"id":77,"slug":78,"title":79,"cover_image":80,"image_url":80,"created_at":81,"category":13},"a0ce6402-ebae-4dbb-95e4-56b2e0dcb819","aider-open-source-coding-agent-repo-edits-en","Aider turns open-source coding into repo edits","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781013807484-ff3a.png","2026-06-09T14:02:56.712253+00:00",[83,88,93,98,103,108,113,118,123,128],{"id":84,"slug":85,"title":86,"created_at":87},"8008f1a9-7a00-4bad-88c9-3eedc9c6b4b1","surepath-ai-mcp-policy-controls-en","SurePath AI's New MCP Policy Controls Enhance AI Security","2026-03-26T01:26:52.222015+00:00",{"id":89,"slug":90,"title":91,"created_at":92},"27e39a8f-b65d-4f7b-a875-859e2b210156","mcp-standard-ai-tools-2026-en","MCP Standard in 2026: Integrating AI Tools","2026-03-26T01:27:43.127519+00:00",{"id":94,"slug":95,"title":96,"created_at":97},"165f9a19-c92d-46ba-b3f0-7125f662921d","rag-2026-transforming-enterprise-ai-en","How RAG in 2026 is Transforming Enterprise AI","2026-03-26T01:28:11.485236+00:00",{"id":99,"slug":100,"title":101,"created_at":102},"6a2a8e6e-b956-49d8-be12-cc47bdc132b2","mastering-ai-prompts-2026-guide-en","Mastering AI Prompts: A 2026 Guide for Developers","2026-03-26T01:29:07.835148+00:00",{"id":104,"slug":105,"title":106,"created_at":107},"3ab2c67e-4664-4c67-a013-687a2f605814","garry-tan-open-sources-claude-code-toolkit-en","Garry Tan Open-Sources a Claude Code Toolkit","2026-03-26T08:26:20.245934+00:00",{"id":109,"slug":110,"title":111,"created_at":112},"66a7cbf8-7e76-41d4-9bbf-eaca9761bf69","github-ai-projects-to-watch-in-2026-en","20 GitHub AI Projects to Watch in 2026","2026-03-26T08:28:09.752027+00:00",{"id":114,"slug":115,"title":116,"created_at":117},"9f332fda-eace-448a-a292-2283951eee71","practical-github-guide-learning-ml-2026-en","A Practical GitHub Guide to Learning ML in 2026","2026-03-27T01:16:50.125678+00:00",{"id":119,"slug":120,"title":121,"created_at":122},"1b1f637d-0f4d-42bd-974b-07b53829144d","aiml-2026-student-ai-ml-lab-repo-review-en","AIML-2026 Is a Bare-Bones Student Lab Repo","2026-03-27T01:21:51.661231+00:00",{"id":124,"slug":125,"title":126,"created_at":127},"6d1bf3f6-e191-4d30-b55b-8a0722fa6afe","ai-trending-github-repos-and-research-feeds-en","AI Trending Tracks Repos and Research Feeds","2026-03-27T01:31:35.709532+00:00",{"id":129,"slug":130,"title":131,"created_at":132},"010539a1-4c3a-4bd3-937a-26616422ee0d","awesome-ai-for-science-research-tools-map-en","Awesome AI for Science Is Becoming a Real Research Map","2026-03-27T01:46:50.89513+00:00"]