# npm

npm is the package manager for the Node JavaScript platform, used to publish, discover, install, and develop Node programs.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret Stealing Malware Via GitHub Actions & npm

DevFeed: [Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret Stealing Malware Via GitHub Actions & npm](<https://devfeed.tech/articles/thousands-of-github-accounts-hijacked-with-wfx-loot-ci-secret-stealing-malware-via-github-actions-npm-131777.md>)

Original publisher: [Read original article](<https://www.ox.security/blog/thousands-of-github-accounts-hijacked-with-wfx-loot-ci-secret-stealing-malware-via-github-actions-npm/>)

Author: Moshe Siman Tov Bustan

Published: 2026-11-12T17:35:37Z

Content type: news

Language: en

Sources: [OX Security](<https://devfeed.tech/sources/ox-security.md>)

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [npm](<https://devfeed.tech/topics/npm.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [malware](<https://devfeed.tech/tags/malware.md>), [npm](<https://devfeed.tech/tags/npm.md>), [research](<https://devfeed.tech/tags/research.md>), [secret](<https://devfeed.tech/tags/secret.md>), [security](<https://devfeed.tech/tags/security.md>), [stealer](<https://devfeed.tech/tags/stealer.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [wfx-loot](<https://devfeed.tech/tags/wfx-loot.md>)

### AI overview

OX Security describes an ongoing campaign in which attackers used 4,837 hijacked GitHub accounts to probe repositories, inject a roughly 1,500-line shell script through GitHub Actions workflows or npm install hooks, then quickly revert commits and delete workflow runs and logs. The script sought GitHub, cloud, package registry, Kubernetes, Vault and AI credentials; at least 1,806 repositories reportedly ran it and exfiltrated secrets. Exfiltration shifted from HTTP servers to Telegram, so blocking known IP addresses alone may not suffice. The article recommends searching for the named pull request, branch and commit patterns; rotating secrets and revoking reachable tokens if malicious code landed; and checking cloud identity and role configurations for persistence. A probe pull request alone is treated as evidence that its submitting account is compromised. The campaign was still active in the reported observations, and private repositories and non-default branches were not visible in the counts.

### Source excerpt

Threat actors used thousands of hijacked GitHub accounts to inject a self-erasing CI secret stealer into tens of thousands of repositories, stealing cloud, package registry and AI credentials Overview OX Security researchers are tracking a large-scale supply chain campaign, dubbed wfx-loot, in which threat actors used 4,837 hijacked GitHub accounts to push a CI secret [...] The post Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret Stealing Malware Via GitHub Actions & npm appeared first on OX Security.

## Vite vs webpack vs npm vs Yarn vs Bun: What's the Difference?

DevFeed: [Vite vs webpack vs npm vs Yarn vs Bun: What's the Difference?](<https://devfeed.tech/articles/vite-vs-webpack-vs-npm-vs-yarn-vs-bun-what-s-the-difference-130197.md>)

Original publisher: [Read original article](<https://hackernoon.com/vite-vs-webpack-vs-npm-vs-yarn-vs-bun-whats-the-difference?source=rss>)

Author: Mohsen

Published: 2026-11-12T07:10:10Z

Content type: comparison

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Bun](<https://devfeed.tech/topics/bun.md>), [Vite](<https://devfeed.tech/topics/vite.md>), [Webpack](<https://devfeed.tech/topics/webpack.md>), [npm](<https://devfeed.tech/topics/npm.md>), [Yarn](<https://devfeed.tech/topics/yarn.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [pnpm](<https://devfeed.tech/topics/pnpm.md>)

Tags: [bun](<https://devfeed.tech/tags/bun.md>), [bun-package-manager](<https://devfeed.tech/tags/bun-package-manager.md>), [difference](<https://devfeed.tech/tags/difference.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [javascript-development](<https://devfeed.tech/tags/javascript-development.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [tools](<https://devfeed.tech/tags/tools.md>), [vite](<https://devfeed.tech/tags/vite.md>), [vs](<https://devfeed.tech/tags/vs.md>), [webpack](<https://devfeed.tech/tags/webpack.md>), [yarn](<https://devfeed.tech/tags/yarn.md>)

### AI overview

JavaScript runtimes, package managers and bundlers do different jobs: Node and Bun run JavaScript, npm, Yarn, pnpm and Bun install dependencies, while webpack and Vite prepare browser code. Vite starts development faster by serving files with limited transformation and bundles for production; webpack bundles during development and offers broad configurability at the cost of more setup and slower starts on large projects. Bun combines runtime, package manager, bundler and test runner. The article's warm-cache Mac test found bun install fastest (about 0.2 seconds versus npm's 2.2 and Yarn 1's 1.15), but this is one project and does not cover cold installs, Yarn 4 or pnpm. It suggests trying Bun as a package manager alongside an existing Node setup; production use as a runtime warrants testing the specific stack, since Node has more production history.

### Source excerpt

Vite vs webpack, npm vs Yarn, and Bun vs Node.js explained. Understand which JavaScript tools compete and which solve completely different problems.

## Vercel Sandbox now supports managed npm credentials

DevFeed: [Vercel Sandbox now supports managed npm credentials](<https://devfeed.tech/articles/vercel-sandbox-now-supports-managed-npm-credentials-133482.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-sandbox-now-supports-managed-npm-credentials>)

Author: Elisabeth Rülke

Published: 2026-11-12T01:56:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [npm](<https://devfeed.tech/topics/npm.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Environment Variables](<https://devfeed.tech/topics/environment-variables.md>), [jfrog artifactory](<https://devfeed.tech/topics/jfrog-artifactory.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [artifactory](<https://devfeed.tech/tags/artifactory.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [github-packages](<https://devfeed.tech/tags/github-packages.md>), [install](<https://devfeed.tech/tags/install.md>), [jfrog-artifactory](<https://devfeed.tech/tags/jfrog-artifactory.md>), [latest](<https://devfeed.tech/tags/latest.md>), [managed](<https://devfeed.tech/tags/managed.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-packages](<https://devfeed.tech/tags/npm-packages.md>), [packages](<https://devfeed.tech/tags/packages.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Sandbox can install private npm packages using credentials stored in team Shared Environment Variables, including from custom registries such as GitHub Packages and JFrog Artifactory. Set `credentials: { npm: true }` when creating a sandbox, then run the package install after placing project files in its working directory. Tokens stay outside the sandbox; the firewall authenticates install requests to configured registries so a coding agent can install dependencies without seeing the tokens. Update the Sandbox SDK or CLI to the latest version.

### Source excerpt

Vercel Sandbox can now install your team's private npm packages using credentials stored in team Shared Environment Variables. Custom registries such as GitHub Packages and JFrog Artifactory are also supported. Pass credentials: { npm: true } when creating a sandbox to let it use your team's existing npm credentials. Tokens stay outside the sandbox. The firewall adds authentication to install requests sent to your configured registries, so a coding agent can install dependencies without seeing the tokens. Update your Sandbox SDK or CLI to the latest version. Read the npm credentials documentation to get started. Read more

## How to Build an MCP Server That Checks npm Packages Before AI Installs Them

DevFeed: [How to Build an MCP Server That Checks npm Packages Before AI Installs Them](<https://devfeed.tech/articles/how-to-build-an-mcp-server-that-checks-npm-packages-before-ai-installs-them-128451.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-to-build-an-mcp-server-that-checks-npm-packages-before-ai-installs-them?source=rss>)

Author: Tarun Singh

Published: 2026-11-11T07:39:09Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [audit](<https://devfeed.tech/tags/audit.md>), [build](<https://devfeed.tech/tags/build.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [cloudflare-workers](<https://devfeed.tech/tags/cloudflare-workers.md>), [deprecation](<https://devfeed.tech/tags/deprecation.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-packages](<https://devfeed.tech/tags/npm-packages.md>), [packages](<https://devfeed.tech/tags/packages.md>), [remote](<https://devfeed.tech/tags/remote.md>), [remote-mcp-server](<https://devfeed.tech/tags/remote-mcp-server.md>), [server](<https://devfeed.tech/tags/server.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

The article builds pkgscout, a stateless MCP server on Cloudflare Workers that checks npm packages before an AI suggests installing them. Its `inspect_package` tool reports package metadata and deprecation, and generates bounded typo variants when a name is missing; npm search can bury deprecated packages, while typo matches may themselves be misleading or malicious, so suggestions include warnings. `check_vulnerabilities` queries npm's advisory database but requires exact versions, rejecting ranges. To stay within Workers' 10 ms CPU limit, the server fetches compact `/latest` manifests instead of large package documents and caches registry calls for five minutes. The excerpt also explains bearer-token authentication, local testing with the SDK's modern protocol negotiation, and deployment. It describes a shared token as suitable for personal use and points to OAuth for team sharing; PyPI support and checks for newly created packages remain proposed additions.

### Source excerpt

Build a remote MCP server on Cloudflare Workers that checks npm packages for typos, deprecation and known vulnerabilities before your AI installs them.

## Static Publishing on Fastly Compute: What's New in v8

DevFeed: [Static Publishing on Fastly Compute: What's New in v8](<https://devfeed.tech/articles/static-publishing-on-fastly-compute-what-s-new-in-v8-129259.md>)

Original publisher: [Read original article](<https://www.fastly.com/blog/static-publishing-fastly-compute-whats-new-v8/>)

Author: Katsuyuki Omuro

Published: 2026-11-11T00:00:00Z

Content type: article

Language: en

Sources: [Fastly Blog](<https://devfeed.tech/sources/fastly-blog.md>)

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [2-0-0](<https://devfeed.tech/tags/2-0-0.md>), [2022](<https://devfeed.tech/tags/2022.md>), [collections](<https://devfeed.tech/tags/collections.md>), [compute](<https://devfeed.tech/tags/compute.md>), [edge](<https://devfeed.tech/tags/edge.md>), [fastly](<https://devfeed.tech/tags/fastly.md>), [js](<https://devfeed.tech/tags/js.md>), [object](<https://devfeed.tech/tags/object.md>), [object-storage](<https://devfeed.tech/tags/object-storage.md>), [preview](<https://devfeed.tech/tags/preview.md>), [publishing](<https://devfeed.tech/tags/publishing.md>), [serve](<https://devfeed.tech/tags/serve.md>), [static](<https://devfeed.tech/tags/static.md>), [storage](<https://devfeed.tech/tags/storage.md>), [support](<https://devfeed.tech/tags/support.md>), [urls](<https://devfeed.tech/tags/urls.md>), [v8](<https://devfeed.tech/tags/v8.md>), [version](<https://devfeed.tech/tags/version.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Version 8 of `@fastly/compute-js-static-publish` serves static sites from Fastly Compute while keeping content separate from the app, so content updates do not require rebuilding the Wasm app. KV Store remains the default: it deduplicates files by content hash and chunks files over 20 MB. Version 8 adds beta support for Fastly Object Storage or S3-compatible storage, where files remain whole and storage costs may be lower. Named collections allow staging and preview versions to coexist, expire, and be promoted to live; the app can select a collection by hostname, cookie, header, path, or Config Store value. Publishing compresses text files and skips unchanged files; optional response caching avoids storage reads on hits, with responses over 8 MiB served directly from storage by default. The generated JavaScript app can be extended with custom request handling. Upgrading from v6 or earlier requires re-scaffolding; v7 KV Store users can install v8 and rebuild/deploy without republishing existing content.

### Source excerpt

Version 8 of Compute JS Static Publish adds Object Storage support, named collections, and preview URLs. Serve static sites from the edge with no origin.

## Ethersphere Hijacked With Crypto Stealing Malware Via Github & npm

DevFeed: [Ethersphere Hijacked With Crypto Stealing Malware Via Github & npm](<https://devfeed.tech/articles/ethersphere-hijacked-with-crypto-stealing-malware-via-github-npm-123003.md>)

Original publisher: [Read original article](<https://www.ox.security/blog/ethersphere-hijacked-with-crypto-stealing-malware-via-github-npm/>)

Author: Moshe Siman Tov Bustan

Published: 2026-11-09T09:29:08Z

Content type: news

Language: en

Sources: [OX Security](<https://devfeed.tech/sources/ox-security.md>)

Topics: [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [Malware](<https://devfeed.tech/topics/malware.md>), [npm](<https://devfeed.tech/topics/npm.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Remote Access Trojan](<https://devfeed.tech/topics/remote-access-trojan.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>)

Tags: [application-security](<https://devfeed.tech/tags/application-security.md>), [backdoors](<https://devfeed.tech/tags/backdoors.md>), [c2](<https://devfeed.tech/tags/c2.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [crypto](<https://devfeed.tech/tags/crypto.md>), [crypto-wallet](<https://devfeed.tech/tags/crypto-wallet.md>), [ethereum](<https://devfeed.tech/tags/ethereum.md>), [github](<https://devfeed.tech/tags/github.md>), [key](<https://devfeed.tech/tags/key.md>), [keys](<https://devfeed.tech/tags/keys.md>), [malware](<https://devfeed.tech/tags/malware.md>), [npm](<https://devfeed.tech/tags/npm.md>), [ox-security](<https://devfeed.tech/tags/ox-security.md>), [research](<https://devfeed.tech/tags/research.md>), [software-supply-chain-security](<https://devfeed.tech/tags/software-supply-chain-security.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [supply-chain-compromise](<https://devfeed.tech/tags/supply-chain-compromise.md>), [wallet](<https://devfeed.tech/tags/wallet.md>)

### AI overview

OX Security reports a coordinated compromise of Ethersphere's @ethersphere/bee-js npm package and swarm-desktop GitHub repository, apparently using a stolen developer access key. Malicious code contacts a command server, collects Swarm configuration and encrypted wallet-key data, then installs platform-specific remote access: ScreenConnect on Windows and the evjawbreaker Go RAT on Linux and macOS; unsupported platforms receive a decoy script. The article says the npm version was revoked but the malicious GitHub release and command server were still live at publication. It estimates exposure at 13,378 monthly package downloads, 3,152 through affected direct dependents, 260 through an indirect dependent, and 44 GitHub release downloads. Recommended steps are to check dependencies and lockfiles, assess wallet credentials as potentially compromised if the code ran, and pin verified clean versions.

### Source excerpt

Threat actors compromised Ethersphere's npm and GitHub packages to steal crypto wallet keys and deploy cross-platform backdoors Overview OX Security researchers identified a coordinated supply chain compromise affecting the Ethersphere ecosystem, a decentralized storage and communication protocol for Ethereum. Threat actors leveraged a suspected compromised developer access key to inject malicious code into both the [...] The post Ethersphere Hijacked With Crypto Stealing Malware Via Github & npm appeared first on OX Security.

## The Binance Hack: Why You Should Never Trust a Coding Assignment

DevFeed: [The Binance Hack: Why You Should Never Trust a Coding Assignment](<https://devfeed.tech/articles/the-binance-hack-why-you-should-never-trust-a-coding-assignment-121774.md>)

Original publisher: [Read original article](<https://jsdev.space/binance-hack-interview/>)

Author: anton liberant

Published: 2026-11-06T00:00:00Z

Content type: article

Language: en

Sources: [JavaScript Development](<https://devfeed.tech/sources/javascript-development.md>)

Topics: [npm security](<https://devfeed.tech/topics/npm-security.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Binance](<https://devfeed.tech/topics/binance.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [binance](<https://devfeed.tech/tags/binance.md>), [binance-hack](<https://devfeed.tech/tags/binance-hack.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-interview](<https://devfeed.tech/tags/coding-interview.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [fake](<https://devfeed.tech/tags/fake.md>), [hack](<https://devfeed.tech/tags/hack.md>), [interview](<https://devfeed.tech/tags/interview.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-packages](<https://devfeed.tech/tags/npm-packages.md>), [packages](<https://devfeed.tech/tags/packages.md>), [security](<https://devfeed.tech/tags/security.md>), [tasks](<https://devfeed.tech/tags/tasks.md>), [tools](<https://devfeed.tech/tags/tools.md>), [trust](<https://devfeed.tech/tags/trust.md>), [vs-code](<https://devfeed.tech/tags/vs-code.md>)

### AI overview

The article's practical takeaway is to treat unfamiliar coding assignments as untrusted code: inspect them before execution and keep them away from work credentials and sensitive systems. It describes Binance's preliminary account of a months-long attack involving a tampered developer tool, a fake interview assignment that reportedly compromised an engineer's computer, lateral movement through an internal AI tool, and a stolen deployment token used to reach wallet-signing infrastructure. The article reports about $6.34 billion in affected assets and says Binance had frozen or intercepted about $2.85 billion by November 3, 2026; figures remain subject to reconciliation, and an independent review was pending. Suggested precautions include reviewing package scripts and editor or container configuration, installing npm dependencies with lifecycle scripts disabled, retaining VS Code Workspace Trust protections, and using a disposable, isolated environment for execution. These checks reduce specific risks but do not make untrusted code safe; running application code can still execute it. The article also recommends that organizations separate interview projects from managed workstations,

### Source excerpt

How a fake coding interview led to the $6.34B Binance hack. Learn how malicious npm packages, VS Code tasks, and developer tools can compromise your machine.

## Docker and ActiveState Extending Secure Defaults to the Packages Developers Install

DevFeed: [Docker and ActiveState Extending Secure Defaults to the Packages Developers Install](<https://devfeed.tech/articles/docker-and-activestate-extending-secure-defaults-to-the-packages-developers-install-119503.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/docker-activestate-trusted-content/>)

Author: Vishrut Iyengar

Published: 2026-11-05T15:28:22Z

Content type: release

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [Docker Hardened Images](<https://devfeed.tech/topics/docker-hardened-images.md>), [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [npm](<https://devfeed.tech/topics/npm.md>), [pip](<https://devfeed.tech/topics/pip.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [artifactory](<https://devfeed.tech/tags/artifactory.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [axios](<https://devfeed.tech/tags/axios.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [built-from-source](<https://devfeed.tech/tags/built-from-source.md>), [content](<https://devfeed.tech/tags/content.md>), [developers](<https://devfeed.tech/tags/developers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-hardened-images](<https://devfeed.tech/tags/docker-hardened-images.md>), [packages](<https://devfeed.tech/tags/packages.md>), [partners](<https://devfeed.tech/tags/partners.md>), [partnerships](<https://devfeed.tech/tags/partnerships.md>), [products](<https://devfeed.tech/tags/products.md>), [secure-defaults](<https://devfeed.tech/tags/secure-defaults.md>), [security](<https://devfeed.tech/tags/security.md>), [solutions](<https://devfeed.tech/tags/solutions.md>), [standard](<https://devfeed.tech/tags/standard.md>), [teams](<https://devfeed.tech/tags/teams.md>), [trusted-supply-chain](<https://devfeed.tech/tags/trusted-supply-chain.md>)

### AI overview

Docker and ActiveState extend supply chain controls from container images to application dependencies. Docker Hardened Images (DHI) are minimal, source-built images with signed SBOMs, SLSA Level 3 provenance, full CVE visibility, and--on paid tiers--a 7-day SLA for critical and high CVEs. ActiveState's Curated Catalog is a policy-governed repository containing team-approved packages, compiled from source with SLSA Level 3 provenance and complete SBOMs; it automatically rebuilds components after upstream fixes, with SLAs of 5 business days for critical CVEs and 10 for high CVEs. Teams can route Artifactory or Nexus through the catalog while developers and coding assistants retain familiar pip and npm workflows. The article says these controls complement pinned digests, cooldown periods, and sandboxed agents; the integration does not replace them.

### Source excerpt

Docker partners with ActiveState to continue to provide one standard for trusted content across everything you and your teams build on.

## PolinRider Returns: Hijacked npm Packages Use Ethereum Blockchain to Conceal Malware Infrastructure

DevFeed: [PolinRider Returns: Hijacked npm Packages Use Ethereum Blockchain to Conceal Malware Infrastructure](<https://devfeed.tech/articles/polinrider-returns-hijacked-npm-packages-use-ethereum-blockchain-to-conceal-malware-infrastructure-119016.md>)

Original publisher: [Read original article](<https://www.ox.security/blog/polinrider-returns-hijacked-npm-packages-use-ethereum-blockchain-to-conceal-malware-infrastructure/>)

Author: Moshe Siman Tov Bustan

Published: 2026-11-04T20:59:06Z

Content type: news

Language: en

Sources: [OX Security](<https://devfeed.tech/sources/ox-security.md>)

Topics: [npm security](<https://devfeed.tech/topics/npm-security.md>), [Malware](<https://devfeed.tech/topics/malware.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [Ethereum](<https://devfeed.tech/topics/ethereum.md>), [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>), [Blockchain](<https://devfeed.tech/topics/blockchain.md>), [npm](<https://devfeed.tech/topics/npm.md>), [infection chain](<https://devfeed.tech/topics/infection-chain.md>), [Cryptocurrency](<https://devfeed.tech/topics/cryptocurrency.md>)

Tags: [appsec](<https://devfeed.tech/tags/appsec.md>), [blockchain](<https://devfeed.tech/tags/blockchain.md>), [c2](<https://devfeed.tech/tags/c2.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [code](<https://devfeed.tech/tags/code.md>), [command](<https://devfeed.tech/tags/command.md>), [command-and-control](<https://devfeed.tech/tags/command-and-control.md>), [control](<https://devfeed.tech/tags/control.md>), [ethereum](<https://devfeed.tech/tags/ethereum.md>), [family](<https://devfeed.tech/tags/family.md>), [hidden](<https://devfeed.tech/tags/hidden.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [ip](<https://devfeed.tech/tags/ip.md>), [loader](<https://devfeed.tech/tags/loader.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [malware](<https://devfeed.tech/tags/malware.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-packages](<https://devfeed.tech/tags/npm-packages.md>), [overview](<https://devfeed.tech/tags/overview.md>), [ox-security](<https://devfeed.tech/tags/ox-security.md>), [packages](<https://devfeed.tech/tags/packages.md>), [polinrider](<https://devfeed.tech/tags/polinrider.md>), [research](<https://devfeed.tech/tags/research.md>)

### AI overview

OX Security reports compromised releases of legitimate npm packages linked to PolinRider. On import, an obfuscated loader queries public Ethereum RPC endpoints for a transaction containing a C2 IP, downloads an XOR-obfuscated JavaScript payload over HTTP, and executes it through an interactive Node.js process, potentially keeping activity in memory. Updating the blockchain reference can redirect affected installations without changing the published package. The affected packages total about 1,400 weekly downloads, a measure of download activity rather than confirmed infections. Recommended steps are to check dependencies and lockfiles against the affected versions, consider accessible wallets and credentials potentially compromised if the code executed, and pin dependencies to verified clean versions or apply a minimum package-age policy.

### Source excerpt

Overview OX Security researchers identified malicious releases of legitimate npm packages compromised in a campaign linked to the PolinRider malware family. The injected code uses the Ethereum blockchain as a dead drop for command-and-control (C2) infrastructure. When an affected package is imported, a hidden loader queries public Ethereum RPC endpoints to retrieve a C2 IP [...] The post PolinRider Returns: Hijacked npm Packages Use Ethereum Blockchain to Conceal Malware Infrastructure appeared first on OX Security.

## Blocking malicious npm packages before and during installation

DevFeed: [Blocking malicious npm packages before and during installation](<https://devfeed.tech/articles/blocking-malicious-npm-packages-before-and-during-installation-112727.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/blocking-malicious-npm-packages-before-and-during-installation>)

Author: Andrew Healey

Published: 2026-11-02T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [npm security](<https://devfeed.tech/topics/npm-security.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [automatically](<https://devfeed.tech/tags/automatically.md>), [blocking](<https://devfeed.tech/tags/blocking.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [builds](<https://devfeed.tech/tags/builds.md>), [cache](<https://devfeed.tech/tags/cache.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [downloads](<https://devfeed.tech/tags/downloads.md>), [error](<https://devfeed.tech/tags/error.md>), [existing](<https://devfeed.tech/tags/existing.md>), [function](<https://devfeed.tech/tags/function.md>), [install](<https://devfeed.tech/tags/install.md>), [installation](<https://devfeed.tech/tags/installation.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [malware](<https://devfeed.tech/tags/malware.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-packages](<https://devfeed.tech/tags/npm-packages.md>), [packages](<https://devfeed.tech/tags/packages.md>)

### AI overview

Vercel checks blocked npm package versions before and during dependency installation to help prevent malicious install scripts from running. Before installation, it scans supported lockfiles, including when dependencies come from the build cache; during installation, it blocks affected public npm downloads. Existing checks of installed dependencies and function outputs continue before deployment. Protections apply automatically to new builds on all plans. When a blocked package is found, Vercel fails the deployment, names the package and version, and attempts to invalidate the affected build cache. Update the dependency and lockfile to a safe version, then redeploy.

### Source excerpt

Vercel now checks for blocked npm packages before and during dependency installation in builds, helping prevent malicious install scripts from running. The checks use a blocklist of specific package versions selected for blocking because of malware or security vulnerabilities, with new rules typically reaching new builds within minutes. Before installation, Vercel checks supported lockfiles, including when dependencies are restored from the build cache. During installation, Vercel blocks affected public npm downloads. Existing checks of installed dependencies and function outputs continue before deployment. These protections apply automatically to new builds on all plans, with no configuration required. If a blocked dependency is detected, Vercel fails the deployment, identifies the package and version in the error, and attempts to invalidate the affected build cache. Update the dependency to a safe version and update the lockfile, then redeploy. Read more

## Measure time to the first working agent integration

DevFeed: [Measure time to the first working agent integration](<https://devfeed.tech/articles/measure-time-to-the-first-working-agent-integration-109715.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/time-to-first-agent-integration>)

Author: Swytchcode Team

Published: 2026-10-30T18:44:00Z

Content type: tutorial

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [lead time](<https://devfeed.tech/topics/lead-time.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-integration](<https://devfeed.tech/tags/agent-integration.md>), [cli](<https://devfeed.tech/tags/cli.md>), [command](<https://devfeed.tech/tags/command.md>), [dry](<https://devfeed.tech/tags/dry.md>), [dry-run](<https://devfeed.tech/tags/dry-run.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [first](<https://devfeed.tech/tags/first.md>), [install](<https://devfeed.tech/tags/install.md>), [integration](<https://devfeed.tech/tags/integration.md>), [machine](<https://devfeed.tech/tags/machine.md>), [run](<https://devfeed.tech/tags/run.md>), [time](<https://devfeed.tech/tags/time.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

The article defines a reproducible setup benchmark: on a clean machine, time from CLI installation through a successful `swy exec ... --dry-run` using a method ID copied from `swy list methods`. Record each command's wall time and exit code, plus the provider, install method, date, and CLI version. Dry run validates the local call without sending it; measure OAuth consent and live-call latency separately. If provider search returns no result, stop and record that the bundle is absent rather than inventing an ID. Report the result for the specific machine, date, and provider, and retain logs across reruns. No measured duration is supplied.

### Source excerpt

Time a clean machine from install through a passing dry run, and write down each command. Publish the log you measured, with the provider and CLI version.

## How to move Squarespace blog posts into the Webflow CMS

DevFeed: [How to move Squarespace blog posts into the Webflow CMS](<https://devfeed.tech/articles/how-to-move-squarespace-blog-posts-into-the-webflow-cms-109629.md>)

Original publisher: [Read original article](<https://www.webflow.com/blog/squarespace-blog-posts-webflow-cms>)

Author: Ismail Ajagbe

Published: 2026-10-30T00:00:00Z

Content type: tutorial

Language: en

Sources: [Webflow Blog](<https://devfeed.tech/sources/webflow-blog.md>)

Topics: [webflow](<https://devfeed.tech/topics/webflow.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [WordPress](<https://devfeed.tech/topics/wordpress.md>), [Data serialization](<https://devfeed.tech/topics/data-serialization.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [archive](<https://devfeed.tech/tags/archive.md>), [blog](<https://devfeed.tech/tags/blog.md>), [blog-posts](<https://devfeed.tech/tags/blog-posts.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [cloudflare-workers](<https://devfeed.tech/tags/cloudflare-workers.md>), [cms](<https://devfeed.tech/tags/cms.md>), [csv](<https://devfeed.tech/tags/csv.md>), [csv-import](<https://devfeed.tech/tags/csv-import.md>), [guides](<https://devfeed.tech/tags/guides.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [import](<https://devfeed.tech/tags/import.md>), [posts](<https://devfeed.tech/tags/posts.md>), [webflow](<https://devfeed.tech/tags/webflow.md>)

### AI overview

For simple archives, Webflow's CSV import may suffice; a custom Webflow Cloud importer provides per-post validation and slug-specific results. The described Next.js 15 app sends JSON records containing title, slug, HTML body, and original publish date to a key-protected route, which creates CMS items as drafts in batches of up to 50. The original date needs its own CMS field because Webflow's system dates reflect import timing. The setup requires a CMS-enabled Premium plan, a Webflow API token with CMS:write, Node.js 22+, and npm. Preserve Squarespace URL paths by matching the collection path or adding redirects. Cloud deployment requires manually including the app's base path in client fetches; the guide also warns against Next.js's unsupported edge runtime and use of node:fs. The importer leaves image URLs pointing to Squarespace, and rich text code blocks may import empty. Review failures and changed slugs, then publish drafts after checking fields and dates.

### Source excerpt

Import Squarespace blog posts into the Webflow CMS with a Webflow Cloud app that keeps original slugs and publish dates.

## One Tool for the (Spell Checking) Job

DevFeed: [One Tool for the (Spell Checking) Job](<https://devfeed.tech/articles/one-tool-for-the-spell-checking-job-107249.md>)

Original publisher: [Read original article](<https://code.dblock.org/2026/10/29/one-tool-for-the-spell-checking-job.html>)

Author: Daniel Doubrovkine (dblock@dblock.org)

Published: 2026-10-29T00:00:00Z

Content type: article

Language: en

Sources: [Daniel Doubrovkine](<https://devfeed.tech/sources/daniel-doubrovkine.md>)

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [Markdown](<https://devfeed.tech/topics/markdown.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [npm](<https://devfeed.tech/topics/npm.md>), [pip](<https://devfeed.tech/topics/pip.md>), [bazel](<https://devfeed.tech/topics/bazel.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [blog](<https://devfeed.tech/tags/blog.md>), [ci](<https://devfeed.tech/tags/ci.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [environment](<https://devfeed.tech/tags/environment.md>), [html](<https://devfeed.tech/tags/html.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [jekyll](<https://devfeed.tech/tags/jekyll.md>), [linter](<https://devfeed.tech/tags/linter.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [plugins](<https://devfeed.tech/tags/plugins.md>), [project](<https://devfeed.tech/tags/project.md>), [python](<https://devfeed.tech/tags/python.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [rust](<https://devfeed.tech/tags/rust.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

The author argues for adding spelling checks as plugins to tools a project already uses, avoiding a separate runtime, configuration, and CI job. They replaced a Python checker that took over three minutes on a Ruby Jekyll blog with a RuboCop plugin, integrating spelling into the existing command and configuration. The listed plugins cover Ruby through RuboCop, Rust through Dylint, Markdown through markdownlint, and Markdown, HTML, plain text, and JavaScript/TypeScript prose through Prettier. The Prettier plugin uses existing syntax trees to separate prose from program structure; an example flags "helo" and suggests alternatives. The author cautions that Copilot initially built that plugin as a wrapper around the markdownlint spellcheck rule.

### Source excerpt

I've built four spell-checking plugins in the last week. This is not an unhealthy interest in spelling. The cost of rolling tools out is the cost of tokens + my time supervising AI. So, before adding another language runtime, package manager, configuration file, and CI job to your project, consider spending an hour vibe coding the missing plugin. This blog used to run a Python spell checker that took more than three minutes. It's a Jekyll blog, which is Ruby. Why was I maintaining a Python environment to tell me that I misspelled "hello"? I replaced it with a RuboCop plugin. Spelling became another cop, with the same configuration, exclusions, command, and CI integration as the rest of the checks. A Rust project shouldn't need my Ruby setup to check its comments. A JavaScript project that already runs Prettier shouldn't need an additional Markdown linter just to check spelling. You can either keep assembling a Frankenstein collection of tools, roll out a custom script, or you can ask AI to build the missing feature. AI loves simplicity and consistent patterns. This approach pays forward. Here's my recent zoo. rubocop-spellcheck adds spelling to RuboCop for Ruby comments, strings, identifiers, Markdown, RDoc, AsciiDoc, and plain text. dylint-spellcheck adds spelling to Dylint for Rust comments, Rustdoc attributes, Markdown, and plain text. markdownlint-rule-spellcheck adds spelling to the Markdown linter you might already be running. prettier-plugin-spellcheck adds spelling to Prettier for Markdown, HTML, plain text, and JavaScript/TypeScript prose. markdownlint-rule-single-line-paragraphs keeps Markdown paragraphs on one source line. Everything builds on top of simple and powerful platforms. The Prettier version is a good example. Prettier already parses Markdown, HTML, JavaScript, and TypeScript. I used its syntax trees to distinguish prose from program structure instead of inventing another parser. Comments and visible text are reasonable things to spellcheck, too

## GitHub's npm package firewall can block brand-new versions before they install

DevFeed: [GitHub's npm package firewall can block brand-new versions before they install](<https://devfeed.tech/articles/github-s-npm-package-firewall-can-block-brand-new-versions-before-they-install-105295.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/10/28/github-package-firewall-npm/>)

Author: Mirko Zorz

Published: 2026-10-28T17:09:14Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>), [npm](<https://devfeed.tech/topics/npm.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [autofix](<https://devfeed.tech/tags/autofix.md>), [build](<https://devfeed.tech/tags/build.md>), [cobol](<https://devfeed.tech/tags/cobol.md>), [code-scanning](<https://devfeed.tech/tags/code-scanning.md>), [code-security](<https://devfeed.tech/tags/code-security.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [github](<https://devfeed.tech/tags/github.md>), [install](<https://devfeed.tech/tags/install.md>), [malware](<https://devfeed.tech/tags/malware.md>), [news](<https://devfeed.tech/tags/news.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-package](<https://devfeed.tech/tags/npm-package.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

GitHub's npm firewall checks packages against enterprise policy before they reach a laptop, build, or coding agent. It blocks known malware, critical vulnerabilities, and brand-new versions; whether a version is new depends on package release-date metadata. Enterprises can create custom policies, including a soak or cooldown period. The three other announced additions address code scanning and remediation: AI Scan checks pull requests for vulnerabilities in languages rule-based scanning may miss, and can scan repositories on demand; a Copilot app extension surfaces code-scanning alerts, including AI Scan findings, before a pull request exists; and Autofix offers reviewable pull-request suggestions or batch Agentic Autofix across GitHub tools and more than 70 partner tools. Dependabot reachability analysis checks whether code calls a vulnerable function and exposes the call path to help teams rank alerts. This overview reflects the supplied article text.

### Source excerpt

GitHub announced a package firewall that checks npm packages against an enterprise's policy before they install. It blocks known malware, critical vulnerabilities, and brand-new versions, and any developer can turn it on by pointing npm at the firewall. The checks run before a package reaches a laptop, a build, or a coding agent. GitHub says AI agents are helping developers build more software, faster, and the firewall is one of four security additions aimed at ... More -> The post GitHub's npm package firewall can block brand-new versions before they install appeared first on Help Net Security.

## Your agent can now publish your docs

DevFeed: [Your agent can now publish your docs](<https://devfeed.tech/articles/your-agent-can-now-publish-your-docs-106831.md>)

Original publisher: [Read original article](<https://www.mintlify.com/blog/mint-deploy>)

Author: Denzell Ford

Published: 2026-10-28T00:00:00Z

Content type: release

Language: en

Sources: [Mintlify Blog](<https://devfeed.tech/sources/mintlify-blog.md>)

Topics: [Publishing](<https://devfeed.tech/topics/publishing.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [npm](<https://devfeed.tech/topics/npm.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [account](<https://devfeed.tech/tags/account.md>), [acme](<https://devfeed.tech/tags/acme.md>), [actions](<https://devfeed.tech/tags/actions.md>), [admin](<https://devfeed.tech/tags/admin.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-workflow](<https://devfeed.tech/tags/agentic-workflow.md>), [agents](<https://devfeed.tech/tags/agents.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [article](<https://devfeed.tech/tags/article.md>), [can](<https://devfeed.tech/tags/can.md>), [docs](<https://devfeed.tech/tags/docs.md>), [github](<https://devfeed.tech/tags/github.md>), [github-repository](<https://devfeed.tech/tags/github-repository.md>), [live](<https://devfeed.tech/tags/live.md>), [repository](<https://devfeed.tech/tags/repository.md>), [site](<https://devfeed.tech/tags/site.md>), [terminal](<https://devfeed.tech/tags/terminal.md>)

### AI overview

The `mint deploy` CLI lets agents publish a live Mintlify docs site without an account or GitHub repository: from the folder containing `docs.json`, run `npm i -g mint` and `mint deploy --subdomain acme`. It creates a hosted Git repository, pushes the docs, and serves the site at `acme.mintlify.site`. The owner must claim the site within 24 hours using an email, sign-in, and code exchange; an unclaimed first site is deleted with its repository when that period expires. For an existing GitHub repository, `mint deploy --github` sets up a GitHub Actions workflow for default-branch updates, but this option applies only before claiming. After claiming, GitHub can be connected in dashboard settings. Agents unable to install the CLI can use the `auth.md` raw HTTP flow.

### Source excerpt

Agents can publish a live Mintlify site from the terminal without an account or GitHub repository. You can claim the site within 24 hours.

## A Difference Without a Distinction: A Measurement Study of Release Trust Evidence in Package Registries

DevFeed: [A Difference Without a Distinction: A Measurement Study of Release Trust Evidence in Package Registries](<https://devfeed.tech/articles/a-difference-without-a-distinction-a-measurement-study-of-release-trust-evidence-in-package-registries-101350.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2606.22593>)

Author: Igor Santos-Grueiro

Published: 2026-10-27T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [pnpm](<https://devfeed.tech/topics/pnpm.md>), [trust](<https://devfeed.tech/topics/trust.md>), [project release](<https://devfeed.tech/topics/project-release.md>), [npm](<https://devfeed.tech/topics/npm.md>), [release engineering](<https://devfeed.tech/topics/release-engineering.md>), [PyPI](<https://devfeed.tech/topics/pypi.md>), [rubygems](<https://devfeed.tech/topics/rubygems.md>)

Tags: [1-6](<https://devfeed.tech/tags/1-6.md>), [2025](<https://devfeed.tech/tags/2025.md>), [account](<https://devfeed.tech/tags/account.md>), [alert](<https://devfeed.tech/tags/alert.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [backports](<https://devfeed.tech/tags/backports.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [branch](<https://devfeed.tech/tags/branch.md>), [central](<https://devfeed.tech/tags/central.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [measurement](<https://devfeed.tech/tags/measurement.md>), [package](<https://devfeed.tech/tags/package.md>), [package-registries](<https://devfeed.tech/tags/package-registries.md>), [registries](<https://devfeed.tech/tags/registries.md>), [release](<https://devfeed.tech/tags/release.md>), [study](<https://devfeed.tech/tags/study.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

The study finds that pnpm's release evidence policy blocks some legitimate updates while detecting only a limited subset of attacks. Replaying pnpm 10.29.3 across 1,997 npm packages, the authors found blocks for 1.6% of popular-package installs and 7.6% of recently updated installs, mostly due to manual backports; semver 6.3.1 accounted for 14 of 16 popular-package failures. The policy can flag an attack only when an earlier version of that package had stronger evidence. In an npm advisory census, that condition held for 17.5% of attacked packages, and attackers with observed access could have added evidence to pass 15 of 17 flagged releases. Full signing-identity pins triggered alerts for 75.8% of packages with multiple keyless-signed releases, often because certificates encode a Git branch or tag. The tested variants did not distinguish recent backports from attacks; the abstract also reports a comparison of release evidence across npm, PyPI, Maven Central, crates.io, and RubyGems but gives no comparative results.

### Source excerpt

arXiv:2606.22593v3 Announce Type: replace-cross Abstract: A stolen npm token or account lets an attacker publish a malicious version of a popular package. Such uploads skip the project's CI workflow and can lack its provenance, so since November 2025 an opt-in pnpm policy refuses any release with weaker evidence than an earlier one. Maintainers also publish backports by hand; how often the policy blocks them and which attacks it flags is unknown. We test the policy on the latest versions of 1,997 popular and recently updated npm packages, replay its variants and identity pins on reconstructed stolen-credential incidents, and analyze an npm malware advisory census. We also compare publication evidence across five package registries: npm, PyPI, Maven Central, crates.io, and RubyGems. With pnpm 10.29.3, 1.6% of popular and 7.6% of recently updated installs are blocked, mostly by backports, and one security fix backported by hand, semver 6.3.1, causes 14 of the 16 popular failures. The policy can flag an attack only if an earlier release of the same package carried stronger evidence. In the census, 17.5% of attacked packages had earlier evidence; two campaigns supply about half of these. Attackers with the observed access could have passed 15 of the 17 flagged releases by adding evidence. Pins on the full signing identity alert on 75.8% of packages with at least two keyless-signed releases, largely because certificates name the Git branch or tag. No variant tells a recent backport and an attack apart: comparing per line or declaring manual lines at the registry admits both, and an age cutoff exempts only old releases.

## How to Check and Update Your Node Version (Windows, Mac, Linux)

DevFeed: [How to Check and Update Your Node Version (Windows, Mac, Linux)](<https://devfeed.tech/articles/how-to-check-and-update-your-node-version-windows-mac-linux-101999.md>)

Original publisher: [Read original article](<https://markodenic.com/check-node-version/>)

Author: Marko

Published: 2026-10-26T20:00:00Z

Content type: tutorial

Language: en

Sources: [Marko Denic Blog](<https://devfeed.tech/sources/marko-denic-blog.md>)

Topics: [version](<https://devfeed.tech/topics/version.md>), [npm](<https://devfeed.tech/topics/npm.md>), [Homebrew](<https://devfeed.tech/topics/homebrew.md>), [Windows](<https://devfeed.tech/topics/windows.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Git](<https://devfeed.tech/topics/git.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [apt](<https://devfeed.tech/tags/apt.md>), [homebrew](<https://devfeed.tech/tags/homebrew.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [nvm](<https://devfeed.tech/tags/nvm.md>), [pin](<https://devfeed.tech/tags/pin.md>), [plus](<https://devfeed.tech/tags/plus.md>), [project](<https://devfeed.tech/tags/project.md>), [run](<https://devfeed.tech/tags/run.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [update](<https://devfeed.tech/tags/update.md>), [version](<https://devfeed.tech/tags/version.md>), [web-development](<https://devfeed.tech/tags/web-development.md>), [windows](<https://devfeed.tech/tags/windows.md>), [winget](<https://devfeed.tech/tags/winget.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Run `node -v` (or `node --version`) to check Node.js; use `npm -v` separately for npm. The article recommends LTS for real projects and identifies Node 24 as the safe default, with Node 26 becoming LTS on 28 October 2026. Version managers such as nvm, nvm-windows, and fnm support switching between versions and pinning a project with `.nvmrc`; nvm-windows requires removing an existing Node installation first. Alternatives include Windows `winget`, macOS Homebrew (where unversioned `node` follows the newest release, including non-LTS), and NodeSource packages for Debian and Ubuntu. Pin versions with `.nvmrc`, document supported versions in `package.json`'s `engines`, and use `actions/setup-node` to align GitHub Actions. After upgrades, npm may need a separate update, global packages may need reinstalling, and native modules may need rebuilding. The text advises checking release notes and tests before major upgrades.

### Source excerpt

Check your Node.js version with node -v, then update it with nvm, fnm, winget, Homebrew or apt. Plus which version to run in late 2026 and how to pin it per project.

## AI coding agents fall for malicious instructions planted in the Downloads folder

DevFeed: [AI coding agents fall for malicious instructions planted in the Downloads folder](<https://devfeed.tech/articles/ai-coding-agents-fall-for-malicious-instructions-planted-in-the-downloads-folder-100440.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/10/26/ai-coding-agents-malware-openai-codex/>)

Author: Sinisa Markovic

Published: 2026-10-26T11:26:40Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [prompt injection](<https://devfeed.tech/topics/prompt-injection.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [malware protection](<https://devfeed.tech/topics/malware-protection.md>), [npm](<https://devfeed.tech/topics/npm.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>)

Tags: [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agents-md](<https://devfeed.tech/tags/agents-md.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsing](<https://devfeed.tech/tags/browsing.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [codex](<https://devfeed.tech/tags/codex.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [downloads](<https://devfeed.tech/tags/downloads.md>), [hot-stuff](<https://devfeed.tech/tags/hot-stuff.md>), [instructions](<https://devfeed.tech/tags/instructions.md>), [login](<https://devfeed.tech/tags/login.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [malware](<https://devfeed.tech/tags/malware.md>), [news](<https://devfeed.tech/tags/news.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-package](<https://devfeed.tech/tags/npm-package.md>), [openai](<https://devfeed.tech/tags/openai.md>), [security](<https://devfeed.tech/tags/security.md>), [token](<https://devfeed.tech/tags/token.md>), [website](<https://devfeed.tech/tags/website.md>)

### AI overview

Forever Security reports that a website can silently place an AGENTS.md file in Downloads, where a coding agent may treat it as trusted instructions when opened there. In tests, Codex followed the planted file in more than 90% of attempts, changed computer-wide settings and installed a named npm package; the package was later removed from npm. The researchers' separate Claude Code test was harder to trigger: about half of attempts redirected requests through an attacker-controlled server, exposing a login token, and roughly one fifth enabled code execution through a helper agent. Most Codex tests used a harmless stand-in; the malicious package was run once in an isolated virtual machine. The researchers advise avoiding coding agents in Downloads, reviewing unfamiliar AGENTS.md or CLAUDE.md files and settings, keeping approval prompts and sandboxes on, and replacing tokens if a planted file is found.

### Source excerpt

A file that a website saves to the Downloads folder without approval can trick AI coding agents into installing a malicious npm package or handing over the user's login token when they're opened in that folder, Forever Security has found. The file is called AGENTS.md, a plain text document developers place in a project folder with instructions for coding agents, the AI tools that write and run code on their own. One turned up on ... More -> The post AI coding agents fall for malicious instructions planted in the Downloads folder appeared first on Help Net Security.

## Your npm install was safe. What happens when the package runs?

DevFeed: [Your npm install was safe. What happens when the package runs?](<https://devfeed.tech/articles/your-npm-install-was-safe-what-happens-when-the-package-runs-100445.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4236783/your-npm-install-was-safe-what-happens-when-the-package-runs.html>)

Author: Sonu Kapoor

Published: 2026-10-26T09:00:00Z

Content type: opinion

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [npm](<https://devfeed.tech/topics/npm.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [branch protection rules](<https://devfeed.tech/topics/branch-protection-rules.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [out-of-process](<https://devfeed.tech/topics/out-of-process.md>)

Tags: [application](<https://devfeed.tech/tags/application.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [application-security-code-security-javascript-libraries-and-frameworks-node-js-programming-lang](<https://devfeed.tech/tags/application-security-code-security-javascript-libraries-and-frameworks-node-js-programming-lang.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [checkmarx](<https://devfeed.tech/tags/checkmarx.md>), [code](<https://devfeed.tech/tags/code.md>), [code-security](<https://devfeed.tech/tags/code-security.md>), [condition](<https://devfeed.tech/tags/condition.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [functions](<https://devfeed.tech/tags/functions.md>), [hooks](<https://devfeed.tech/tags/hooks.md>), [import](<https://devfeed.tech/tags/import.md>), [install](<https://devfeed.tech/tags/install.md>), [installation](<https://devfeed.tech/tags/installation.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [libraries-and-frameworks](<https://devfeed.tech/tags/libraries-and-frameworks.md>), [library](<https://devfeed.tech/tags/library.md>), [loader](<https://devfeed.tech/tags/loader.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [network](<https://devfeed.tech/tags/network.md>), [node](<https://devfeed.tech/tags/node.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-package](<https://devfeed.tech/tags/npm-package.md>), [package](<https://devfeed.tech/tags/package.md>), [programming-languages](<https://devfeed.tech/tags/programming-languages.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-feature](<https://devfeed.tech/tags/storytype-feature.md>)

### AI overview

Blocking npm lifecycle scripts prevents package code from running during installation, but does not establish that a dependency is safe at runtime. Checkmarx Zero reported a malicious look-alike of `sorted-btree` with no malicious install hook; its trigger was inside `BTree.prototype.set` and required a particular key condition. The excerpt recommends reviewing dependency diffs and exact resolved artifacts for new or unexpected packages, testing uncertain packages with realistic calls in an isolated environment, and limiting the secrets, filesystem, process, and network access available to processes using third-party code. These checks reduce risk but cannot prove every hidden path is safe.

### Source excerpt

For years, one of the first questions we asked about a suspicious npm package was whether it ran a pre-install or postinstall script. Those hooks can execute before a developer has written a line of code that uses the dependency. Blocking them is a sensible defense. It prevents a particular kind of package from running just because someone installed it. But installation is only the beginning of a package's life in an application. Once that application starts, it calls the package's functions with its own permissions, environment variables, network access, and data. A package can behave impeccably during installation and still become dangerous when the application uses it. That distinction is the lesson of the recently disclosed indexed-btree campaign. Checkmarx Zero found a malicious npm package that imitated the legitimate sorted-btree library. The package had no malicious install hook. Its loader sat inside BTree.prototype.set, a method the application would call as part of normal use. The reported trigger checked for a particular key value before launching an obfuscated file in a separate Node process. Merely installing the package did not trigger that behavior; neither would an import alone necessarily do so. The application had to reach the relevant method and condition. The precise key and second-stage machinery are useful to incident responders. The larger design failure is simpler: an install-time policy can tell us whether a package executed during installation. It cannot tell us whether code inside that package is safe to execute later. The wrong boundary When a team turns off life-cycle scripts, its installation process becomes safer in a specific, measurable way. npm's ignore-scripts setting prevents scripts declared in package.json from running during installation. npm also offers controls for approving install-time scripts. Neither mechanism claims to inspect every branch of a library's runtime code. We sometimes talk as though a quiet install means a

## npm uninstall: How to Remove (and Update) npm Packages

DevFeed: [npm uninstall: How to Remove (and Update) npm Packages](<https://devfeed.tech/articles/npm-uninstall-how-to-remove-and-update-npm-packages-99224.md>)

Original publisher: [Read original article](<https://markodenic.com/npm-uninstall-package/>)

Author: Marko

Published: 2026-10-25T09:00:00Z

Content type: tutorial

Language: en

Sources: [Marko Denic Blog](<https://devfeed.tech/sources/marko-denic-blog.md>)

Topics: [npm](<https://devfeed.tech/topics/npm.md>), [Package Management](<https://devfeed.tech/topics/package-management.md>)

Tags: [dependencies](<https://devfeed.tech/tags/dependencies.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [dev](<https://devfeed.tech/tags/dev.md>), [eslint](<https://devfeed.tech/tags/eslint.md>), [global](<https://devfeed.tech/tags/global.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [install](<https://devfeed.tech/tags/install.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [latest](<https://devfeed.tech/tags/latest.md>), [latest-tag](<https://devfeed.tech/tags/latest-tag.md>), [local](<https://devfeed.tech/tags/local.md>), [major](<https://devfeed.tech/tags/major.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-packages](<https://devfeed.tech/tags/npm-packages.md>), [npx](<https://devfeed.tech/tags/npx.md>), [package](<https://devfeed.tech/tags/package.md>), [package-json](<https://devfeed.tech/tags/package-json.md>), [pnpm](<https://devfeed.tech/tags/pnpm.md>), [project](<https://devfeed.tech/tags/project.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [update](<https://devfeed.tech/tags/update.md>), [web-development](<https://devfeed.tech/tags/web-development.md>), [yarn](<https://devfeed.tech/tags/yarn.md>)

### AI overview

`npm uninstall <package>` removes a package from `node_modules`, `package.json`, and `package-lock.json`; it works for dependencies and dev dependencies, and multiple names can be supplied. Global packages require `-g`. For a clean reinstall matching the lock file, `npm ci` deletes `node_modules` and fails if the lock file conflicts with `package.json`; `npm install` can update the lock file. `npm outdated` shows newer versions, while `npm update` stays within declared version ranges and does not cross major versions. For latest major releases, the excerpt recommends updating ranges with `npm-check-updates` or installing `@latest`, then reviewing changelogs and running tests. `npm ls` can show why a package remains installed, and Knip can identify unused dependencies. The excerpt advises using one package manager per project to avoid conflicting lock files.

### Source excerpt

How to uninstall npm packages: local, dev and global packages, several at once, everything in node_modules, finding unused dependencies, plus how to update all packages and the yarn and pnpm equivalents.

## Introducing Markdownlint Spellcheck

DevFeed: [Introducing Markdownlint Spellcheck](<https://devfeed.tech/articles/introducing-markdownlint-spellcheck-96431.md>)

Original publisher: [Read original article](<https://code.dblock.org/2026/10/22/introducing-markdownlint-rule-spellcheck.html>)

Author: Daniel Doubrovkine (dblock@dblock.org)

Published: 2026-10-22T00:00:00Z

Content type: release

Language: en

Sources: [Daniel Doubrovkine](<https://devfeed.tech/sources/daniel-doubrovkine.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [npm](<https://devfeed.tech/topics/npm.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [english](<https://devfeed.tech/tags/english.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [jekyll](<https://devfeed.tech/tags/jekyll.md>), [liquid](<https://devfeed.tech/tags/liquid.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npx](<https://devfeed.tech/tags/npx.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [rust](<https://devfeed.tech/tags/rust.md>), [technical-documentation](<https://devfeed.tech/tags/technical-documentation.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

markdownlint-rule-spellcheck 0.1.0 adds CSpell-powered spelling checks to Markdown through markdownlint-cli2, requires Node.js 22.18 or later, and includes American English without a separate dictionary or system spelling package. It checks headings, paragraphs, lists, tables, link labels, image descriptions, and--by default--YAML front matter; it skips code, links' destinations, URLs, email addresses, and Liquid tags and expressions. Project vocabulary can be collected, reviewed for typos, and added to a custom dictionary. Autocorrection is opt-in and only applies when the first suggestion is one edit away; the excerpt recommends reviewing changes because a correctly spelled suggestion may still be the wrong word. Checking front matter requires a markdownlint-cli2 setting that leaves it visible to custom rules, which can also expose it to other Markdown rules, or front matter checking can be disabled.

### Source excerpt

After RuboCop spelling checks for Ruby and Dylint spelling checks for Rust, here's the version that doesn't require either language's toolchain. Introducing markdownlint-rule-spellcheck, a custom markdownlint rule powered by CSpell. Released 0.1.0 checks Markdown prose, suggests corrections, and ships American English through its dependencies. No separate dictionary download or system spelling package is required. Getting Started Requires Node.js 22.18 or later. Install the rule and the command-line runner: npm install --save-dev markdownlint-cli2 markdownlint-rule-spellcheck@0.1.0 Add .markdownlint-cli2.jsonc: { "customRules": ["markdownlint-rule-spellcheck"] } Given example.md: # Say helo to the world Run: npx markdownlint-cli2 example.md The spelling diagnostic includes the original line and column: example.md:1:7 error spellcheck Prose words should be spelled correctly [Misspelled word: "helo". Suggestions: hello, helio, halo.] Headings, paragraphs, lists, tables, link labels, and image descriptions are checked. Code, link destinations, URLs, and email addresses are skipped. Liquid expressions and tags are skipped too, which matters for Jekyll sites like this one. Accepting Project Vocabulary Technical documentation contains legitimate words that aren't in an English dictionary. Collect candidates, review them, and add the accepted words: npx markdownlint-rule-spellcheck collect "**/*.md" --output .spellcheck.txt # Edit .spellcheck.txt: remove actual typos. npx markdownlint-rule-spellcheck add ./.spellcheck.txt npx markdownlint-cli2 "**/*.md" The add command updates .markdownlint.json, preserving existing settings. Its dictionary configuration looks like this: { "spellcheck": { "dictionaries": { "en": ["@cspell/dict-en_us", "./.spellcheck.txt"] } } } Corrections and Front Matter Corrections are opt-in. Set "autocorrect": true inside spellcheck, then run: npx markdownlint-cli2 --fix "**/*.md" The first suggestion must be one edit away: an insertion, deletion, sub

## How to Diagnose vite: not found After npm ci in a Container Build

DevFeed: [How to Diagnose vite: not found After npm ci in a Container Build](<https://devfeed.tech/articles/how-to-diagnose-vite-not-found-after-npm-ci-in-a-container-build-93154.md>)

Original publisher: [Read original article](<https://www.freecodecamp.org/news/diagnose-vite-not-found-npm-ci-container-build/>)

Author: Ahmed Tariq

Published: 2026-10-21T16:03:14Z

Content type: tutorial

Language: en

Sources: [Free Code Camp](<https://devfeed.tech/sources/freecodecamp-programming-tutorials-python-javascript-git-more.md>)

Topics: [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [npm](<https://devfeed.tech/topics/npm.md>), [Vite](<https://devfeed.tech/topics/vite.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [azure](<https://devfeed.tech/tags/azure.md>), [build](<https://devfeed.tech/tags/build.md>), [build-tool](<https://devfeed.tech/tags/build-tool.md>), [build-tools](<https://devfeed.tech/tags/build-tools.md>), [cache](<https://devfeed.tech/tags/cache.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cli](<https://devfeed.tech/tags/cli.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [development-environment](<https://devfeed.tech/tags/development-environment.md>), [docker](<https://devfeed.tech/tags/docker.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [vite](<https://devfeed.tech/tags/vite.md>)

### AI overview

The `vite: not found` error followed a failed `npm ci`: 528 lockfile entries pointed to an internal package proxy unreachable from the Azure Container Registry build, leaving `node_modules` empty. The tutorial traces the failure by checking the dependency directory, inventorying `resolved` URL hosts, and inspecting earlier npm errors; `Exit handler never called!` alone does not identify the cause. For confirmed public packages, it rewrites only the approved URL prefix while preserving versions and integrity values, then guards each independent install with `npm ci --include=dev` and an executable check for Vite. It recommends verifying the rewrite count, remaining hosts, dependency identity, build, and output. Private packages need a reachable authenticated registry; substituting their URLs may be unsafe.

### Source excerpt

I recently worked on a project where a Node.js application used Vite to compile its frontend. It worked in a browser-hosted development environment, but its image build failed after the move to Azure

## Dependabot now supports npm 12, pnpm 11 and 12, and Bun 1.4

DevFeed: [Dependabot now supports npm 12, pnpm 11 and 12, and Bun 1.4](<https://devfeed.tech/articles/dependabot-now-supports-npm-12-pnpm-11-and-12-and-bun-1-4-90900.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-10-20-dependabot-now-supports-npm-12-pnpm-11-and-12-and-bun-1-4>)

Author: Allison

Published: 2026-10-20T13:52:38Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [npm](<https://devfeed.tech/topics/npm.md>), [pnpm](<https://devfeed.tech/topics/pnpm.md>), [Bun](<https://devfeed.tech/topics/bun.md>)

Tags: [bun](<https://devfeed.tech/tags/bun.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [npm](<https://devfeed.tech/tags/npm.md>), [pnpm](<https://devfeed.tech/tags/pnpm.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

### AI overview

Dependabot now supports npm 12, pnpm 11 and 12, and Bun 1.4, so projects can upgrade to these versions and continue receiving Dependabot updates. Support is available to all github.com users and is slated for GitHub Enterprise Server 3.24. The excerpt points to Dependabot's supported ecosystems and repositories list for the full version coverage.

### Source excerpt

You can now upgrade your projects to npm 12, pnpm 11 or 12, or Bun 1.4 and keep receiving Dependabot updates. Support for these package manager versions is available to... The post Dependabot now supports npm 12, pnpm 11 and 12, and Bun 1.4 appeared first on The GitHub Blog.

## pnpm 11.28.6

DevFeed: [pnpm 11.28.6](<https://devfeed.tech/articles/pnpm-11-28-6-88114.md>)

Original publisher: [Read original article](<https://pnpm.io/blog/releases/11.28.6>)

Author: Zoltan Kochan

Published: 2026-10-15T00:00:00Z

Content type: release

Language: en

Sources: [pnpm](<https://devfeed.tech/sources/pnpm-blog.md>)

Topics: [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [identity](<https://devfeed.tech/tags/identity.md>), [pnpm](<https://devfeed.tech/tags/pnpm.md>)

### AI overview

pnpm 11.28.6 prevents pnpm publish from sending a CI identity token to a registry that it was not issued for. The release also fixes optional peer dependency resolution, configuration handling, workspace installs, deployment, and other package management issues.

### Source excerpt

This release stops pnpm publish from sending a CI identity token to a registry it was not issued for. It also fixes installs that dropped a dependency also declared as an optional peer, and accepts empty httpProxy and httpsProxy settings again.

[Next page](<https://devfeed.tech/topics/npm.md?cursor=WyIyMDI2LTEwLTE1VDAwOjAwOjAwKzAwOjAwIiwgIjdlZWVmMTU3LTJiNGYtNGEwMy05ZGFkLTc4ZTMxZDY1Yjg5OCJd>)