CodeScoring Launches CodeScoring.Save Artifact Repository for Secure Enterprise Development
CodeScoring has unveiled its own artifact repository, CodeScoring.Save, aimed at organizations that need a reliable, on-premises solution for storing and distributing software packages, libraries, container images, and other development components.
The new product is positioned for the corporate segment and companies of any scale that require a predictable and fault-tolerant artifact repository. According to Dmitry Klyuchnikov, head of product development at CodeScoring, the solution was developed in the Go language with a focus on modern Kubernetes environments and secure development standards.
Save belongs to the same category as Sonatype Nexus Repository, JFrog Artifactory, and Harbor. It ships with an automated migration tool from public repositories and supports simultaneous hosting of internal artifacts and proxying of external ones. The repository offers native support for Maven, npm, NuGet, PyPI, Go Modules, Docker/OCI, DEB, RPM, and raw files.
Deployed via Helm in Kubernetes, the system includes role-based access control, dedicated accounts for automation, system and user activity auditing, and a REST API. Compute and storage layers are separated to allow independent scaling.
A key architectural feature is built-in security integration: CodeScoring.Save connects directly with CodeScoring.OSA so that vulnerability information can be viewed inside the repository. The company stresses that Save remains a fully independent product that can be purchased with or without the main CodeScoring platform.
While OSA Proxy validates incoming packages against security policies, Save focuses on storage and distribution. Their integration creates a single trusted entry point that prevents malicious components from entering the development environment. CodeScoring also plans to extend Save to handle AI models, beginning with storage and distribution capabilities for platforms such as Hugging Face, and intends to pursue certification aligned with Russian secure development requirements.
Related articles
WordPress to Automatically Block High-Risk Plugin Updates Before Distribution
WordPress is introducing an automated security screening process for every new plugin release before it reaches millions of sites through the WordPress.org API. Updates flagged with high risk will be blocked from automatic installation, giving developers time to address issues. Previously, only initial plugin submissions were reviewed, while subsequent versions could introduce vulnerabilities, backdoors, or malicious ownership changes without checks. Each release now undergoes a six-hour delay under the Protect The Shire initiative, where multiple AI models and Jetpack Scan analyze changes to produce a combined risk score. High-risk updates are withheld from auto-updates, and developers receive detailed reports. The system has already proven effective by catching a backdoor in a plugin with around 20,000 active installations on July 28, preventing distribution after Wordfence notification. Developers can fix problems and resubmit, or appeal results, though fixing is usually faster than manual review.
Twitch Enhanced Viewer Extension Leaks OAuth Tokens From Nearly 31,000 Users
The browser extension Twitch Enhanced Viewer | JeetBot, available in the official Chrome Web Store and Mozilla Add-ons, secretly forwarded OAuth session tokens to proxies controlled by its operator. These bearer tokens allow full account takeover without passwords or second-factor authentication, enabling actions such as reading and sending whispers, posting in chat, and modifying account settings. The issue surfaced prominently in the v85.x branch where tokens were appended as the &auth= query parameter during network redirects to operator-controlled proxy servers, exposing them in clear text within proxy logs. Earlier v4.x versions had already transmitted tokens via POST requests to a set-token endpoint and backup servers on deno.dev and deno.net. A fix appeared in Firefox version 85.8.7 that stops token exfiltration by altering playlist retrieval, while a Chrome patch is in preparation. Users are advised to uninstall the extension immediately, revoke all active Twitch sessions, and review recent account activity for signs of unauthorized use.
Twitch Enhanced Viewer Extension Leaks OAuth Tokens from Nearly 31,000 Users
The browser extension Twitch Enhanced Viewer | JeetBot, available in the official Chrome Web Store and Mozilla Add-ons, secretly forwarded OAuth session tokens to proxies controlled by its operator. These bearer tokens allow full account takeover without passwords or second-factor authentication, enabling actions such as reading and sending whispers, posting in chat, and modifying account settings. The issue became especially severe in the v85.x branch, where tokens were appended as the &auth= query parameter during network redirects to the operator’s proxy servers, exposing them in clear text within proxy logs. Earlier versions had already transmitted tokens via POST requests to a set-token endpoint and maintained backup endpoints on deno.dev and deno.net. A fix is available in Firefox starting with version 85.8.7, which stops token exfiltration by changing the playlist retrieval method, while a corresponding Chrome patch is in preparation. Users are advised to uninstall the extension immediately, revoke all active Twitch sessions, and review recent account activity for signs of unauthorized use.
Widespread AI Outage Exposes Fragile Cloud Dependencies Behind ChatGPT, Claude and Grok
On September 3, major AI services including ChatGPT, Claude, Grok, Copilot and Gemini suffered a simultaneous outage lasting nearly four hours. The incident began around 9:30 a.m. ET with ChatGPT and rapidly spread, generating over 12,000 reports on Downdetector within twenty minutes. Industry analysis points to underlying cloud infrastructure rather than the models themselves, with Microsoft Azure and Cloudflare identified as the most likely points of failure. Developers relying on tools such as Cursor experienced immediate loss of code completion and intelligent assistance, forcing manual workflows. The event highlighted single points of failure created by heavy concentration of AI workloads on a small number of cloud providers. Security professionals are urged to map AI supply chains, prepare fallback procedures, monitor infrastructure status pages and adopt multi-vendor routing for critical operations.