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
Vendor Responsibility in Open Source: Licensing Obligations Exposed by Sonatype Nexus Changes
The article examines how vendors building products on copyleft open source projects like Nexus Repository OSS inherit significant legal and security responsibilities under licenses such as EPL 1.0. Sonatype's February 2025 shift from regular OSS binary releases to a limited Community Edition forces downstream vendors to handle their own builds, patch porting, and compliance disclosures. This change highlights the second part of copyleft licenses that outlines obligations for distributors, including revealing modifications and assuming liability for the final product. Security implications arise because critical vulnerabilities in the upstream project must now be tracked and patched by the vendor, with delays creating measurable supply chain risks. The piece provides a practical checklist for buyers to assess licensing hygiene, SBOM availability, and vulnerability response times in any open source-based solution.
PhantomSub Campaign Deploys 101 Malicious npm Packages to Hijack WhatsApp Accounts for Unauthorized Channel Subscriptions
Researchers at OX Security uncovered 101 malicious npm packages tied to the PhantomSub campaign that abuse connected WhatsApp accounts to subscribe users to promotional channels without consent. The packages disguise themselves as modified versions of the open-source Baileys library used for WhatsApp automation. Attackers rely on authenticated sessions rather than simple package installation, allowing them to control subscriptions through lists stored on GitHub, in plaintext, or as encoded identifiers. The packages have accumulated roughly 490,000 downloads, including 116,000 in the past 30 days, though the exact number of compromised accounts remains unknown. As of 28 September, npm had removed only 16 of the identified packages. The operation ultimately benefits channels selling bots, game resources, accounts, and promotion services by inflating subscriber counts while disabling notifications to hide the activity.
AI Model Hallucinations Fuel Slopsquatting Attacks on PyPI and npm Registries
Researchers identified 139 package names consistently hallucinated by five different AI models across Python and JavaScript ecosystems. Seven of these names are already registered on PyPI and npm, including one previously used to distribute malware. The attack vector, termed slopsquatting, allows attackers to register AI-suggested package names and execute code with developer privileges during installation. One package, metro-evaluator, contained malicious code removed by npm in December 2025, while another empty package css-color-stop began receiving downloads after the list was published. Real projects such as odf and lusid now occupy names that AI models recommend, causing developers to install unrelated software. Studies show hallucination rates between 4.62% and 21.7% depending on the model, with commercial models performing better than open-source ones. The findings highlight risks when AI coding agents execute dependency installation commands without human verification.
Sapper Revives Minefield to Deliver Accurate SBOM-Based Vulnerability Impact Reports for Cyber Resilience Act Compliance
Developer Perruer has forked the archived BitBom project Minefield into a new open-source tool called Sapper, fixing critical bugs in dependency graph construction and vulnerability matching. The original Minefield used roaring bitmaps and Tarjan's algorithm to build transitive dependency caches from SBOMs in O(n + m) time, but it incorrectly interpreted SPDX edge directions from protobom 0.6, creating false cycles and massively inflating dependent package counts. Additional fixes addressed SQLite memory database pooling issues, OSV range sorting errors with Go pseudo-versions and ECOSYSTEM ecosystems, and slow OSV ingestion by adding a package name index. Sapper now produces prioritized reports using CISA KEV and EPSS scores, showing exact shortest paths from vulnerable packages to root products while respecting OpenVEX statements. The tool maintains full air-gapped operation and supports CycloneDX 1.3–1.7 and SPDX 2.x formats. These improvements directly help organizations meet the 24-hour notification requirements under the EU Cyber Resilience Act for actively exploited vulnerabilities.