# software packages Published articles for software packages. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## @mastra npm scope takeover: 143 packages backdoored via compromised contributor account DevFeed: [@mastra npm scope takeover: 143 packages backdoored via compromised contributor account]() Original publisher: [Read original article]() Published: 2026-06-17T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [npm](), [Malware](), [Remote Access Trojan](), [Cryptocurrency](), [C2]() Tags: [c2](), [chainguard-libraries](), [chainguard-packages](), [command-and-control](), [crypto](), [malware](), [mastra](), [npm](), [npm-takeover](), [packages](), [provenance](), [remote-access](), [remote-access-trojan](), [secure-packages](), [software-packages](), [supply-chain](), [tls]() ### AI overview The article reports that an attacker used a compromised former contributor account to republish all 143 packages in the @mastra npm scope on June 17, 2026. The malicious versions could disable TLS verification, download a cryptocurrency wallet stealer and remote access trojan, and establish command-and-control access. It recommends auditing dependency trees and lockfiles and rotating credentials on affected hosts. ### Source excerpt A supply chain attack compromised all 143 @mastra packages. Chainguard customers stayed protected through malware blocking and source-built libraries. ## Introducing Chainguard OS Packages: Secure ingredients for custom container builds DevFeed: [Introducing Chainguard OS Packages: Secure ingredients for custom container builds]() Original publisher: [Read original article]() Published: 2026-03-17T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard os](), [container images](), [Docker Hardened Images](), [Vulnerabilities](), [Linux](), [Automation](), [Dockerfile](), [Open Source](), [bazel](), [chainguard sboms](), [APK]() Tags: [apk](), [apko](), [automation](), [base-images](), [bazel](), [chainguard](), [chainguard-containers](), [chainguard-libraries](), [chainguard-os](), [chainguard-os-packages](), [chainguard-packages](), [chainguard-sboms](), [container](), [container-images](), [cve](), [dockerfiles](), [open-source](), [sboms](), [secure-software-packages](), [software-packages](), [vulnerabilities](), [zero-cve-packages]() ### AI overview Chainguard introduces Chainguard OS Packages, a service providing continuously maintained, enterprise-grade packages and base images for teams that build custom container images. Customers retain control over image composition and build tooling while Chainguard handles package sourcing, rebuilding, vulnerability remediation, and SBOM generation. ### Source excerpt Chainguard OS Packages are enterprise-grade, zero-CVE packages and base images built and continuously maintained in the Chainguard Factory. ## How to enable Debian 12 Backports repository DevFeed: [How to enable Debian 12 Backports repository]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-05-11T11:02:39Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Debian](), [Package Management](), [apt](), [Package manager](), [Linux]() Tags: [apt](), [apt-cache](), [debian](), [debian-linux](), [dependencies](), [easy](), [how-to](), [install](), [linux](), [package-management](), [packages](), [software-packages]() ### AI overview A tutorial on enabling and using the Debian 12 Bookworm Backports repository. It covers configuring the repository, updating package lists, searching for packages, installing selected backported packages, listing installed backports, and removing them. ### Source excerpt The Debian Linux 12 backports repository offers updated versions of software packages for Debian Stable releases. These packages are sourced from Testing (and sometimes Unstable) branches of Debian, and then optimized and recompiled to function on the current Stable release, such as Bookworm. Let us see how to install and use Debian Linux 12 "Bookworm" Backports repository. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How to enable Debian 12 Backports repository appeared first on nixCraft. ## 100 days of postmarketOS DevFeed: [100 days of postmarketOS]() Original publisher: [Read original article]() Published: 2017-09-03T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [Mobile](), [Software](), [Package Management](), [Android](), [qemu]() Tags: [alpine-linux](), [android](), [command-line](), [developers](), [distribution](), [linux](), [postmarketos](), [software](), [software-packages]() ### AI overview A 100-day progress report on postmarketOS, an alternative Linux-based mobile operating system built by adapting Alpine Linux rather than forking Android. The project uses small Alpine packages, aims to minimize device-specific maintenance, and includes QEMU support for experimentation and development. ### Source excerpt Sustainable Approach For Linux on Phones We are building an alternative to Android and other mobile operating systems by not forking but bending the time-proven Alpine Linux distribution to fit our purpose. Instead of using Android's build process, we build small software packages that can be installed with Alpine's package manager. To minimize the amount of effort for maintenance, we want every device to require only one device-specific package and share everything else. At this point our OS is only suitable for fellow hackers who enjoy using the command-line and want to improve postmarketOS. Telephony or other typical smartphone tasks are not working yet. Why We Evolve in Many Directions Why don't we focus on one "flagship" device and stop making blog posts until it can be used as daily driver? Our philosophy is that community-based FLOSS projects need to become known during the development phase to fellow developers. Our way of doing that is through periodically posting reports summarizing our real progress. The postmarketOS community is a collective group of hackers who contribute to this project in their free time. We won't tell someone who wants to, for example, extend postmarketOS to run Doom on their smartwatch that their idea has no benefit to the project's vision. Such activities demonstrate the flexibility of postmarketOS and oftentimes leads to improvements to the project's codebase as new requirements are implemented to cover previously unforeseen use cases. In addition, these fun activities also increase our collective knowledge about the software and hardware we work with. But most importantly we don't want to, or plan to, take the fun away. Because without being fun and rewarding, a free time project becomes a dead project. It's not all about running Doom though, there are also individuals in the project who have the most fun by actually bringing the project towards this daily-driver vision. Read on to learn about both the incredibly beneficial effor ## Debian Repository Manager DevFeed: [Debian Repository Manager]() Original publisher: [Read original article]() Published: 2014-05-12T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [Debian](), [Tool](), [Repositories](), [Package Management](), [Ruby](), [Git](), [qemu]() Tags: [debian](), [git](), [less](), [manage](), [manager](), [qemu](), [repository](), [ruby](), [software-packages]() ### AI overview The article introduces dr, an open-source Ruby tool for setting up and managing small Debian repositories. It provides a unified interface for repository setup, package building, versioning, distribution, signing, and release management, with Git integration and support for tools such as reprepro, debhelper, debuild, and qemu. ### Source excerpt Set up and manage your own Debian repository with less effort ## Making Your Local Hadoop more like AWS Elastic MapReduce DevFeed: [Making Your Local Hadoop more like AWS Elastic MapReduce]() Original publisher: [Read original article]() Published: 2014-01-02T11:21:13Z Content type: tutorial Language: en Sources: [Ian Hummel]() Topics: [Hadoop](), [Amazon S3](), [configuration](), [Homebrew](), [Development](), [Package manager](), [Compression](), [Unix]() Tags: [analytics](), [aws](), [compression](), [config](), [configuration](), [dev](), [emr](), [hadoop](), [install](), [local](), [s3](), [software-packages](), [unix]() ### AI overview This tutorial explains how to configure a local Hadoop environment to more closely match AWS Elastic MapReduce. It covers using s3:// URIs, embedding AWS access keys, enabling transparent LZO compression, and installing Hadoop with Homebrew, including the distinction between s3:// and s3n:// handling in HDFS. ### Source excerpt At MediaMath we're big users of Elastic MapReduce. EMR's incredible flexibility makes it a great fit for our analytics jobs. An extremely important best practice for any analytics project is to ensure your local dev and test environments match your production environment as much as possible. This eliminates the nasty surprise of launching a job that takes hours only to discover that it fails late into the run due to some unmet dependency or config mistake. Failing to invest time in the dev/test phase is a surefire way to blow big $$. Lately I've been investigating some configuration settings you can make to your local Hadoop to bring it inline with what you'll find when you run a job on an EMR cluster. This is especially important to us since we use S3 as a sort of centralized filesystem and EMR is designed to work wonderfully with S3. Specifically: Using s3:// URIs everywhere instead of s3n:// URIs Embedding AWS access keys Supporting transparent LZO compression Installing Hadoop I run all my Hadoop jobs on my laptop using Homebrew. Homebrew is a fantastic package manager for OS X that makes it a breeze to install general UNIX utilities as well as more complicated software packages (like Hadoop and Hive). $> brew install hadoop And you're good! s3:// vs s3n:// URIs in HDFS Ever wondered what the difference between an s3:// URI and an s3n:// URI is? Essentially up until December, 2010 S3 had a 5GB object size limit. So, if you used the default S3 HDFS implementation (by specifying an s3n:// URI) you couldn't read/write files greater than 5GB. That said, when you did read or write a file with HDFS there was a 1 to 1 correspondence with the object that got stored in S3. To process files larger than 5GB you had to use s3:// URIs in HDFS which actually chunked the file into multiple pieces behind the scenes before storing each piece as a separate object in S3. So when accessing something via HDFS with an s3://bucket/object URI you might actually be downloading multiple