# source Published articles for source. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Babel in Khan Academy's i18n Toolchain DevFeed: [Babel in Khan Academy's i18n Toolchain]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-06-22T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [Babel](), [Internationalization (i18n)](), [toolchain](), [es6](), [JavaScript](), [Parser](), [Universal Syntax Tree.](), [Open Source]() Tags: [api](), [architecture](), [babel](), [build](), [build-system](), [code](), [engineering](), [es6](), [eslint](), [frontend](), [javascript](), [news](), [plugin](), [source](), [structure](), [syntax](), [tests](), [toolchain](), [types](), [web-frontend](), [workflow]() ### AI overview Khan Academy describes switching its ES6 and JSX frontend compilation from jstransform to Babel. The article explains a custom Babel plugin for preserving the project's internationalization behavior and discusses matching generated output, line numbers, whitespace, and the existing build chain. ### Source excerpt By Kevin Barabash We've been using ES6 (along with JSX) for sometime at Khan Academy. Right now, we're ... Read more ## RBP Tracker: Counting the CVE IDs the CVE List Cannot See DevFeed: [RBP Tracker: Counting the CVE IDs the CVE List Cannot See]() Original publisher: [Read original article]() Author: jgamblin Published: 2026-09-14T14:16:42Z Content type: article Language: en Sources: [Jerry Gamblin]() Topics: [data](), [NVD](), [API](), [GitHub]() Tags: [api](), [cve](), [cve-list](), [data](), [ids](), [list](), [nvd](), [report](), [scanner](), [source](), [state](), [uncategorized]() ### AI overview The article examines a corrected RogoLabs tracker for Reserved but Public CVE IDs. It explains that the CVE Services API returns 404 for reserved IDs, while a separate unauthenticated endpoint reveals their RESERVED state. The tracker lists IDs from public advisory feeds and describes how reserved records are absent from the bulk CVE List until publication. ### Source excerpt A new RogoLabs site lists Reserved but Public CVE IDs: 2,315 of them on September 14, drawn from 17 public advisory feeds, refreshed every six hours, and held a week before they appear. The first version of this tracker reported that none of the CVE IDs it found existed in the CVE List, in any ... Read more ## Removing Drivers For Outdated ARM Platforms Will Lighten The Kernel By ~247k Lines DevFeed: [Removing Drivers For Outdated ARM Platforms Will Lighten The Kernel By ~247k Lines]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-14T13:32:47Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [Arm](), [Code](), [Git]() Tags: [code](), [desktop-linux](), [developer](), [drivers](), [git](), [kernel](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [platforms](), [source](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview Linux is removing support for obsolete 32-bit ARM platforms and their associated drivers. The changes could delete roughly 247,000 lines of code, likely in Linux 7.5, although the kernel source tree contains nearly 41 million lines overall. ### Source excerpt The Linux kernel is going to see the removal of a number of recently deprecated ARM 32-bit platforms. Following the deprecation in Linux 7.3, removing the old ARM platforms will lighten the kernel by around 55k lines of code. But removing now unused drivers only relevant to those platforms will mean roughly a quarter million lines of code can be removed from the kernel source tree... ## Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork DevFeed: [Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork]() Original publisher: [Read original article]() Author: Sajid Ali Published: 2026-09-14T04:24:43Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [compose-multiplatform](), [tvOS](), [Kotlin Multiplatform](), [Gradle]() Tags: [apple](), [build](), [compiler](), [compose-multiplatform](), [gradle](), [gradle-plugin](), [ios](), [jetbrains](), [multiplatform](), [source]() ### AI overview This tutorial explains the build setup for adding tvOS support to a Compose Multiplatform fork. It covers Kotlin Multiplatform targets, source-set organization shared between iOS and tvOS, and the build-layer work used to identify missing modules and dependencies. ### Source excerpt Compose Multiplatform on tvOS This series: Compose Multiplatform on tvOS My Journey Making Compose Multiplatform Work on tvOS, and What I Learned Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork (this post) Rendering (coming soon) Siri Remote input (coming soon) Siri Remote trackpad (coming soon) Screen density and text input (coming soon) Porting tv-material (coming soon) The Gradle plugin and third-party libraries (coming soon) Maintaining the fork (coming soon) Building a real app on it (coming soon) Part 1 was why this fork exists. This one is the build layer, and it comes before any Compose code, because in Kotlin Multiplatform a target is not a flag you flip at the end. It decides which source sets compile, which dependencies resolve, which klibs get published, which linker flags get passed. Until the build knows about tvosArm64, nothing tells you what is missing. So the first commits were build files. Once the targets were on, the compiler listed what was missing, module by module, and I worked through that list. Source set layout on the tvos branch I started on a branch called tvos, based on upstream. Back then JetBrains called iOS "uikit" in this repository and the source set was uikitMain. Because tvOS is also UIKit underneath, it made sense to have a common source parent for both iOS and tvOS. But iOS was already being called uikit, so I chose uiKitCommonMain as the source set name and moved all the UIKit files there, keeping only the iOS specific files in uikitMain and putting the tvOS specific files in a new source set, tvosMain. The problem with this approach was how to keep up with upstream. I tried a symlink to the uikit source set, and then overriding the tvOS files in a separate target. The override worked but complicated the process. At that time my goal was to make it runnable on tvOS however possible, so we would have a proof of concept. So I did a lot of hacks in the tvos branch to make it runnable, and af ## Athena spotlight: Black Duck on the importance of flagging zero-days at scale DevFeed: [Athena spotlight: Black Duck on the importance of flagging zero-days at scale]() Original publisher: [Read original article]() Published: 2026-09-14T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Vulnerabilities](), [Artificial Intelligence](), [Frontier AI](), [Frontier Model](), [Security](), [Open Source]() Tags: [ai](), [anthropic](), [athena](), [attacks](), [chainguard](), [code](), [container-images](), [frontier-ai](), [frontier-ai-models](), [frontier-model](), [management](), [mythos](), [open-source](), [osv](), [project-glasswing](), [scale](), [security](), [source](), [vulnerabilities]() ### AI overview The article explains how Black Duck and the Athena coalition address the growing volume of AI-discovered open source zero-day vulnerabilities. Athena members use frontier models to scan sandboxed applications, while Chainguard triages, validates, and remediates findings and shares artifacts and OSV data. Black Duck uses that feed to alert customers and provide mitigation and remediation guidance. ### Source excerpt AI can find zero-days faster than teams can fix them. See how Black Duck and Athena work together to turn findings into actionable protection. ## Intel Reverses Decision To Cancel Their Open-Source Font Project DevFeed: [Intel Reverses Decision To Cancel Their Open-Source Font Project]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-12T13:45:00Z Content type: news Language: en Sources: [Phoronix]() Topics: [Font](), [intel](), [Open Source](), [GitHub]() Tags: [cost](), [desktop-linux](), [developers](), [github](), [intel](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [source](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview Intel reversed its decision to archive Intel One Mono, an open-source monospaced font for developers. The project had been archived after limited recent activity but was restored two days later and will remain maintained. The article also notes the discontinuation or archiving of several other Intel open-source projects. ### Source excerpt Amid Intel cutting back on open-source projects over the past two years as cost cutting measures at the company, their latest open-source project on the chopping block was the peculiar font they developed a few years back. The project was archived this week only to change course two days later... ## Vercel for Platforms can now deploy from your users' GitHub repositories DevFeed: [Vercel for Platforms can now deploy from your users' GitHub repositories]() Original publisher: [Read original article]() Author: Cody Wong Published: 2026-08-18T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [GitHub](), [Deployment](), [App]() Tags: [deployment](), [github](), [source](), [tokens](), [vercel]() ### AI overview Vercel for Platforms can deploy directly from users' GitHub repositories without requiring installation of the Vercel GitHub App. Deployments use a read-only, repository-scoped gitAccessToken that is valid for 24 hours or less; Vercel temporarily stores it in encrypted form for source retrieval and does not store it on the deployment. ### Source excerpt Teams building on Vercel for Platforms can now create deployments directly from their users' GitHub repositories, without requiring them to install the Vercel GitHub App. When creating a deployment, pass a gitAccessToken alongside gitSource. Vercel uses the token to retrieve the source and build the deployment. Tokens should be read-only, scoped to the requested repository, and valid for 24 hours or less. Vercel temporarily stores the token in encrypted form so source retrieval can complete. The token is never stored on the deployment. Learn more about using a GitHub access token. Read more ## Backblaze Drive Stats: How an Open Dataset Powers Academic and AI/ML Research DevFeed: [Backblaze Drive Stats: How an Open Dataset Powers Academic and AI/ML Research]() Original publisher: [Read original article]() Author: Stephanie Doyle Published: 2026-08-13T15:08:38Z Content type: article Language: en Sources: [Backblaze Blog | Cloud Storage & Cloud Backup]() Topics: [dataset](), [DRIVE](), [Machine learning](), [Transformer](), [Disk image]() Tags: [ai-ml](), [articles](), [b2cloud](), [cloud-storage](), [data](), [drive](), [featured](), [featured-cloud-storage](), [hard-drive-stats](), [ml](), [research](), [source](), [storage]() ### AI overview The article explains how Backblaze Drive Stats evolved from an internal hard-drive reliability tool into an open dataset used in academic and AI/ML research. It describes the dataset's real-world scale, quarterly publication, SMART attributes, labeled failures, broad manufacturer coverage, and use in hard-drive failure prediction research. ### Source excerpt Backblaze Drive Stats has been cited in more than 105 academic papers and AI/ML projects since 2018. Explore the research it powers and download the dataset. The post Backblaze Drive Stats: How an Open Dataset Powers Academic and AI/ML Research appeared first on Backblaze Blog | Cloud Storage & Cloud Backup ## Don't stop early: Case-folding source code at memory speed DevFeed: [Don't stop early: Case-folding source code at memory speed]() Original publisher: [Read original article]() Author: Alexander Neubeck Published: 2026-07-31T16:00:00Z Content type: article Language: en Sources: [GitHub]() Topics: [Optimization](), [Code](), [FIRST](), [Rust]() Tags: [architecture-optimization](), [case-folding](), [code-search](), [engineering](), [github](), [open-source](), [optimization](), [rust](), [source](), [speed]() ### AI overview GitHub explains how it optimized case folding for source-code search. A branch-free ASCII fast path and byte-space arithmetic allow the open-source Rust casefold crate to process code at more than 45 GiB/s on a single core. ### Source excerpt How a branch-free loop and byte-space arithmetic let GitHub case-fold every byte of code search at >45 GiB/s on a single core. The post Don't stop early: Case-folding source code at memory speed appeared first on The GitHub Blog. ## Vercel Sandbox supports forking DevFeed: [Vercel Sandbox supports forking]() Original publisher: [Read original article]() Author: Harpreet Arora Published: 2026-07-28T04:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [SDKs](), [Command-line interface](), [Template]() Tags: [agent](), [cli](), [config](), [documentation](), [fork](), [sdk](), [source](), [upgrade](), [vercel]() ### AI overview Vercel Sandbox now supports forking through Sandbox.fork(), allowing a sandbox to be created from the source's latest saved snapshot while inheriting configuration and environment variables. Forks can be used with the SDK or CLI and support overriding inherited parameters. ### Source excerpt Vercel Sandbox now supports forking with Sandbox.fork(). The fork starts from the source's current snapshot and inherits its config and environment variables. If the source is running, it forks the latest saved state, not the live in-memory state. If the source has no snapshot, it falls back to a fresh create, using the source's runtime and config. Any parameter you pass overrides the inherited value. A fork takes about the same time as creating a sandbox, with the same limits. Use it to branch an agent from a shared base, give each tenant its own copy of a template, or run variations of one setup in parallel. To fork a sandbox with the SDK: To fork a sandbox with the CLI: To get started, upgrade to the latest version: pnpm install @vercel/sandbox@latest # SDK pnpm install -g sandbox@latest # CLI Learn more in the Sandbox documentation. Read more ## Один файл, одна команда: как мы упростили запуск dev-окружения с помощью Runium DevFeed: [Один файл, одна команда: как мы упростили запуск dev-окружения с помощью Runium]() Original publisher: [Read original article]() Author: thebeastapp ("Лаборатория Касперского") Published: 2026-07-24T14:18:59Z Content type: tutorial Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [Development](), [Open Source](), [JSON](), [Docker](), [npm]() Tags: [dev](), [docker](), [javascript](), [json](), [node-js](), [npm](), [open-source](), [runium](), [source](), [tag-369149f96d73](), [tag-6c1e3d9c9659]() ### AI overview This article describes Runium, an open-source tool developed to simplify local development-environment setup. It uses a JSON file to define the environment, allowing projects to be started, stopped, and checked with one command. The article explains the problem Runium addresses, its origins, implementation, comparisons with other approaches, and an example project. ### Source excerpt Локальный запуск dev-окружения в крупном проекте может превратиться в отдельный квест: несколько процессов, Docker-контейнеры, переменные окружения, порядок старта, ожидание готовности сервисов и отличия между ОС. Даже если у вас есть подобный опыт, это может быть неудобно, долго и утомительно. Новичку же обычно не обойтись без длинной подробной инструкции. Привет, Хабр! На связи Сергей Зверьков, старший разработчик в "Лаборатории Касперского". Хочу рассказать, как мы решили эту проблему, написав собственный open-source-инструмент -- Runium. Суть его в том, что он позволяет описать dev-окружение в JSON-файле. После этого проект можно запускать, останавливать и проверять одной командой. В статье расскажу, из какой боли вырос Runium, как он устроен, сравню его с другими решениями и покажу пример использования на простом веб-проекте. Приступим! Читать далее ## Introducing AURA: Building an Open Agentic harness for production AI DevFeed: [Introducing AURA: Building an Open Agentic harness for production AI]() Original publisher: [Read original article]() Author: Henry Andrews Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Agent Harness](), [Platform Engineering](), [Open Source](), [Orchestration](), [Artificial Intelligence](), [telemetry](), [Rust](), [Model Context Protocol](), [Retrieval Augmented Generation (RAG)]() Tags: [agentic](), [agents](), [ai](), [ai-agents](), [building](), [mcp](), [observability](), [open](), [open-source](), [orchestration](), [platform-engineering](), [platforms](), [rag](), [rust](), [source]() ### AI overview AURA is Mezmo's open-source, Rust-based agent harness for running production AI workflows. It provides declarative composition, multi-agent orchestration, MCP tool integration, RAG pipelines, and observability-oriented context for operational investigations. ### Source excerpt AI agents need production infrastructure. AURA is Mezmo's open-source agentic harness, offering declarative composition, multi-agent orchestration, and deep observability ## DSLs Enable Reliable Use of LLMs DevFeed: [DSLs Enable Reliable Use of LLMs]() Original publisher: [Read original article]() Author: Martin Fowler (martin@martinfowler.com) Published: 2026-07-14T12:51:00Z Content type: article Language: en Sources: [Martin Fowler]() Topics: [Large Language Model](), [Code](), [Software](), [systems]() Tags: [article](), [code](), [generate](), [llms](), [software](), [source](), [systems]() ### AI overview The article explains how abstractions and Domain-Specific Languages (DSLs) can provide clear boundaries that make LLM-generated code more reliable. Using Tickloom as an example, it presents an LLM as a partner for iteratively developing a DSL and as a natural-language interface to that DSL, which can serve as a source of truth for software systems. ### Source excerpt LLMs generate code incredibly fast, but to ensure they generate exactly what is intended, they need clear boundaries. Abstractions and Domain-Specific Languages (DSLs) provide a strong harness that guides LLMs right from the start. Unmesh Joshi describes how the example of Tickloom - a domain model and DSL for illustrating distributed system behavior - shows how we can use an LLM as a partner to iteratively build a DSL and as a natural language interface to use it. Such a DSL can act as the key source of truth for software systems in the world of LLMs. more... ## Funding Open Source Without The Bait And Switch: Analytics, Native Maps, TV And More DevFeed: [Funding Open Source Without The Bait And Switch: Analytics, Native Maps, TV And More]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-26T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Open Source](), [GNU General Public License](), [API](), [Android](), [iOS](), [Code]() Tags: [analytics](), [android](), [api](), [ios](), [maps](), [native](), [open-source](), [source]() ### AI overview A Codename One release post describes new analytics, native and vector maps, Apple TV and Android TV support, rich text and code editors, and device integrity APIs. It also explains the project's funding model, including GPL licensing with the Classpath Exception and paid build-cloud capacity. ### Source excerpt A privacy-first analytics API, vector and native maps, Apple TV and Android TV, rich text and code editors, and device integrity APIs, plus how we fund the project without the usual open source bait and switch. ## One year with Codeberg DevFeed: [One year with Codeberg]() Original publisher: [Read original article]() Author: Ludovic Courtès Published: 2026-06-22T14:00:00Z Content type: article Language: en Sources: [GNU Guix -- Blog]() Topics: [pull-requests](), [hosting](), [issue tracking](), [decision-making](), [Git](), [forgejo]() Tags: [article](), [change](), [collaboration](), [community](), [decision-making](), [forgejo](), [issue-tracking](), [pull-requests](), [source]() ### AI overview Guix describes its migration to Codeberg for source code hosting, issue tracking, and pull requests after more than a decade using Savannah, email-based bug reports, patches, and Debbugs. The article discusses the reasons for the change, the project's collective decision-making process, and early takeaways after one year. ### Source excerpt A year ago, Guix migrated to Codeberg for source code hosting, issue tracking, and pull requests. This is a significant change for a project with more than 400 people contributing code each year, after more than decade hosting code at Savannah and dealing with bug reports and patches by email, tracked by a Debbugs instance . This article discusses the process that led to this change and lists some takeaways, a year later. The non-obvious choice For years before, the question of our choice of source code hosting and collaboration tools would regularly come up. However, with... ## Local Qwen isn't a worse Opus, it's a different tool DevFeed: [Local Qwen isn't a worse Opus, it's a different tool]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2026-06-17T00:00:00Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [qwen](), [Claude](), [Artificial Intelligence]() Tags: [agents](), [ai](), [ai-tools](), [claude](), [gpu](), [llm](), [localai](), [qwen](), [source]() ### AI overview The author shares a founder's experience using local Qwen models in a small software business and open source projects. The models have provided useful, specific value, but the author still does not trust them unsupervised because of infinite loops and hallucination risks, especially after quantization for a consumer GPU. ### Source excerpt We've all heard people say that Qwen is near-Opus level, but I have receipts and am here to be transparent with you. ## New AMD Radeon Developer Tool Suite update brings shader source code, Extended PIX Markers, and command-line capture DevFeed: [New AMD Radeon Developer Tool Suite update brings shader source code, Extended PIX Markers, and command-line capture]() Original publisher: [Read original article]() Author: Chris Hesik Published: 2026-06-11T16:26:00Z Content type: release Language: en Sources: [AMD GPUOpen]() Topics: [GPU](), [shaders](), [Ray Tracing](), [Command-line interface](), [Software](), [Hardware]() Tags: [agility-sdk](), [amd](), [announcement](), [command-line](), [developer](), [directx](), [driver](), [gpu](), [gpu-open-tools](), [gpuopen-other-amd](), [gpuopen-tools](), [graphics-apis](), [hardware](), [memory](), [microsoft](), [microsoft-agility-sdk](), [microsoft-directx](), [news](), [optimization](), [other-amd](), [performance](), [product-blogs](), [product-release](), [profiling](), [radeon-developer-panel](), [radeon-developer-tool-suite](), [radeon-gpu-analyzer](), [radeon-gpu-detective](), [radeon-gpu-profiler](), [radeon-memory-visualizer](), [radeon-raytracing-analyzer](), [ray-tracing](), [raytracing](), [rdp](), [rdts](), [release](), [rga](), [rgd](), [rgp](), [rmv](), [rra](), [shaders](), [source](), [technical-articles](), [tool](), [tools]() ### AI overview AMD's Radeon Developer Tool Suite update adds shader source code viewing, instruction-level divergence metrics, and Extended PIX Marker support in RGP 2.7. It also expands hardware compatibility and updates other tools in the suite. ### Source excerpt The new AMD Radeon Developer Tool Suite release delivers RGP 2.7 with shader source code viewing, instruction-level divergence metrics, and Extended PIX Marker support, expanded hardware compatibility, and updates across RGD, RRA, RMV, RGA, and RDP. ## DeltaDB: Version Control for Agent Conversations and Evolving Worktrees DevFeed: [DeltaDB: Version Control for Agent Conversations and Evolving Worktrees]() Original publisher: [Read original article]() Author: Nathan Sobo Published: 2026-06-11T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Software](), [coding](), [Git](), [pull-requests]() Tags: [agents](), [code](), [collaboration](), [files](), [git](), [pull-requests](), [software](), [source](), [terminal](), [version-control]() ### AI overview Zed introduces DeltaDB, a version-control system that records fine-grained code changes alongside the conversations that produce them. It is designed for worktrees edited concurrently by people and agents, with references anchored to individual deltas. ### Source excerpt Agents turned the conversation into the real source of our software. DeltaDB is the version control built for it. ## The expanding threat landscape: Chainguard now scans source code for traditional malware and "greyware" DevFeed: [The expanding threat landscape: Chainguard now scans source code for traditional malware and "greyware"]() Original publisher: [Read original article]() Published: 2026-06-09T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [Malware](), [Code](), [Open Source](), [npm](), [npm packages](), [Security]() Tags: [chainguard](), [chainguard-libraries](), [ecosystems](), [greyware](), [greyware-scanner](), [hardening](), [javascript](), [malware](), [malware-prevention](), [malware-scanner](), [npm](), [npm-packages](), [open-source](), [packages](), [scanner](), [security](), [source](), [supply-chain-attacks]() ### AI overview Chainguard has introduced a source code scanner that detects traditional malware and "greyware," harmful packages that may perform actions such as credential theft, command interception, API key harvesting, or persistent remote access. The scanner currently protects npm packages, scans more than 100,000 packages daily, and has blocked more than 52,000 packages identified as malware or greyware. ### Source excerpt Chainguard's new scanner blocks malware and 'greyware' before it reaches developers, protecting 100,000+ packages daily across open source ecosystems. ## Protected Source Maps: Ship browser source maps securely DevFeed: [Protected Source Maps: Ship browser source maps securely]() Original publisher: [Read original article]() Author: z0oks Published: 2026-05-14T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Authentication](), [debug](), [Deployment](), [Code]() Tags: [authentication](), [browser](), [code](), [debug](), [deployment](), [documentation](), [learn](), [production](), [source](), [vercel]() ### AI overview Vercel's Protected Source Maps restrict access to production browser source maps through Vercel Authentication. Team members can retrieve the maps for readable stack traces and original source files, while other users receive a 404. The feature is enabled by default for new projects, and existing projects can enable it in Deployment Protection settings without redeploying. ### Source excerpt You can now restrict access to production source maps with Protected Source Maps, which puts browser .map files behind Vercel Authentication. Your team can fetch them; everyone else gets a 404. Source maps are how you debug minified production code. They give you readable stack traces and your original source code, with the real filenames and line numbers intact. New projects have Protected Source Maps enabled by default. Existing projects can opt in from Settings -> Deployment Protection, with no redeploy needed. Learn more in the documentation. Read more ## OpenCL 3.1 is Here DevFeed: [OpenCL 3.1 is Here]() Original publisher: [Read original article]() Author: Khronos Group (webservices@khronosgroup.org) Published: 2026-05-04T07:01:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [cross-platform](), [Compiler](), [Open Source](), [toolchain]() Tags: [2026](), [api](), [blog-openc](), [compilation](), [compiler](), [compilers](), [cross-platform](), [directx](), [embedded](), [enumerate](), [opencl](), [optional](), [source](), [spir](), [vulkan]() ### AI overview The Khronos OpenCL Working Group has released OpenCL 3.1, moving field-proven capabilities into the core specification. The release mandates SPIR-V kernel ingestion for conformant implementations and expands cross-platform availability through a growing implementation, compiler, runtime, and framework ecosystem. ### Source excerpt On the eve of IWOCL 2026, the Khronos® OpenCL Working Group has released OpenCL™ 3.1, bringing widely deployed, field-proven capabilities into the core specification to expand functionality, including SPIR-V ingestion, that developers will be able to rely on across conformant implementations. The new specification arrives into a growing OpenCL ecosystem, with implementations from multiple silicon vendors, particularly in mobile and embedded markets, and higher-level frameworks including SYCL™ and chipStar increasingly targeting OpenCL as an acceleration backend. The open-source compiler and runtime ecosystem around OpenCL also continues to mature with layered implementations of OpenCL over Vulkan and DirectX 12 -- widening OpenCL's cross-platform availability, including on platforms without native drivers. ## Seedance 2.0 Video Generation on AI Gateway DevFeed: [Seedance 2.0 Video Generation on AI Gateway]() Original publisher: [Read original article]() Author: Jerilyn Zheng Published: 2026-04-15T08:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Artificial Intelligence](), [vercel ai sdk](), [SDKs](), [multimodal]() Tags: [ai](), [ai-gateway](), [audio](), [cost](), [generation](), [image](), [image-to-video](), [model](), [multimodal](), [playground](), [sdk](), [source](), [speech](), [text-to-video](), [video]() ### AI overview Vercel announces that Bytedance's Seedance 2.0 video generation model is available through AI Gateway in Standard and Fast variants. The model supports text-to-video, image-to-video, multimodal reference-to-video, video editing and extension, synchronized multilingual audio, camera movements, multi-shot composition, and in-video text rendering. ### Source excerpt You can now access Bytedance's latest state-of-the-art video generation model, Seedance 2.0, via AI Gateway with no other provider accounts required. Seedance 2.0 is available on AI Gateway in two variants: Standard and Fast. Both share the same capabilities. Standard produces the highest quality output, while Fast prioritizes generation speed and lower cost. Seedance 2.0 is strong at maintaining motion stability and fine detail across frames, producing consistent output even in complex scenes with facial expressions and physical interactions. The model also generates synchronized audio natively, with support for speech in multiple languages and dialects. Beyond text-to-video and image-to-video, Seedance 2.0 adds multimodal reference-to-video, letting you combine image, video, and audio inputs as reference material in a single generation. It also supports video editing and video extension, along with professional camera movements, multi-shot composition, and in-video text rendering. To use this model, set model to bytedance/seedance-2.0 or bytedance/seedance-2.0-fast in the AI SDK or try it out in the AI Gateway Playground. Text to Video Generate video from a text prompt. Describe the scene, camera movement, and audio for the model to produce. Image to Video Generate video from a starting image. The model animates the image based on the text prompt while preserving the visual content of the source frame. Reference to Video Generate video using image, video, or audio references as source material. You can combine multiple reference types in a single generation to control visual style, motion, and sound. AI Gateway does not charge any markup on video generation: Seedance 2.0 and 2.0 Fast are at the same price as going direct to the Bytedance provider. Learn more about AI Gateway, view the AI Gateway model leaderboard or try it in our model playground. Read more ## Is Grype a single point of failure for Chainguard's CVE detection? DevFeed: [Is Grype a single point of failure for Chainguard's CVE detection?]() Original publisher: [Read original article]() Published: 2026-04-10T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [grype](), [chainguard](), [Malware](), [chainguard containers](), [Open Source](), [Containers]() Tags: [chainguard](), [chainguard-containers](), [chainguard-os](), [chainguard-scanners](), [containers](), [cve](), [grype](), [malware](), [open-source](), [source](), [supply-chain-attacks](), [trivy]() ### AI overview The article explains why Grype is not a single point of failure in Chainguard's CVE detection system. It describes layered defenses including building Grype from source, malware detection, and alternative input-source protections to improve the reliability of security findings. ### Source excerpt Is Grype a single point of failure? Learn how Chainguard uses layered defenses, source builds, and multiple data sources to ensure trusted CVE detection. ## The Promise of Ethereum: Introducing the EF Mandate DevFeed: [The Promise of Ethereum: Introducing the EF Mandate]() Original publisher: [Read original article]() Author: Ethereum Foundation Published: 2026-03-13T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Publishing](), [Open Source](), [Protocol (disambiguation)]() Tags: [ethereum](), [open-source](), [organizational](), [protocol](), [source]() ### AI overview The Ethereum Foundation is publishing the EF Mandate, a document that sets out its purpose, decision-making principles, and responsibilities. The mandate emphasizes Ethereum's commitment to user self-sovereignty, censorship resistance, open source, privacy, security, and resistance to extraction. ### Source excerpt Dearest Friends, Today we are publishing the EF Mandate, a document that serves as part constitution, part manifesto, and part guide for the Ethereum Foundation. It is written primarily for the EF itself: to be clear about what we are here to do, the principles by which we... [Next page]()