Drupal.org vs npm

After the PHP security release: auditing your Drupal sites

Updating PHP closes the door, but it does not tell you whether anyone came through it first. With honeypot evidence of exploitation attempts from 17 October, four days before the fix was public, here is how the Drupal Association is auditing Drupal.org, and what our research suggests site owners should check on their own servers.

Why npm and pnpm audit miss vulnerabilities

This technical article explains why npm and pnpm audit commands can produce conflicting results and miss vulnerabilities. It clarifies that audit is a network request to the registry's audit endpoint, relying solely on the GitHub Advisory Database. The piece identifies four structural gaps: single-source dependency, silent failure without network, npm-ecosystem exclusivity, and lack of reachability analysis or inventory output. The differences between npm and pnpm audit stem from how each resolves the dependency tree and the timing of data. The author recommends a more robust approach: using lockfile-based scanning with aggregated open advisory data like OSV, and producing CycloneDX SBOMs for durable coverage. The article is technical and applicable to developers concerned with supply chain security.

• npm audit and pnpm audit are network requests to a registry endpoint, not local scanners.
• Advisory data for npm and pnpm audit comes from the GitHub Advisory Database.
• The commands can disagree due to differences in dependency tree resolution, devDependencies inclusion, and timing.

10 AI Coding Actions Developers Must Always Review

A developer describes how they use AI to generate code but enforces strict review rules. The article lists ten specific actions the author never allows an AI coding assistant to perform without human verification — including running terminal commands blindly, installing unknown packages, exposing .env secrets, writing authentication or security logic without review, running database migrations immediately, making large project-wide edits, merging code they can't explain, trusting AI-generated tests automatically, letting AI make security decisions alone, and deploying straight to production. The author recommends a simple review workflow (generate, read, understand, test, review diff, then merge) and emphasizes that humans remain responsible for the final result.

• The author uses AI to help generate components, write APIs, fix bugs, explain errors, create tests, refactor code, write SQL, and plan features.
• They list 10 things not to let AI do without checking, including running terminal commands blindly, installing unknown packages, and touching .env secrets carelessly.
• The author warns against running AI-generated database migrations or deploying AI-written code straight to production without review and testing.

Practical Guide to React Performance

This technical guide summarizes practical, high-impact techniques for improving React application performance. It advises measuring with the React Profiler and browser performance tools before optimizing, avoiding unnecessary re-renders by stabilizing referential identity (useMemo, useCallback, React.memo), and using code-splitting and lazy loading to ship less JavaScript. The guide recommends moving heavy work to the server with React Server Components (preferring server components for data fetching and static content, and client components for interactivity), and optimizing images and fonts via responsive sizes, modern formats, and lazy loading. The author emphasizes that fixing a small set of common patterns resolves most real-world React performance problems.

• Measure before optimizing using the React Profiler and the browser's performance panel.
• Avoid unnecessary re-renders by stabilizing derived data and callbacks with useMemo and useCallback and by using React.memo for expensive children.
• The article recommends installing a single dependency to let the React Compiler handle memoization: npm install babel-plugin-react-compiler.