CYBERSECURITYTRACKER
Permanent story citation

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

This page keeps the story as Cybersecurity Tracker first published it. If the tracker later corrects it, the correction appears below the original and never replaces it.

Back to newsStory 11628

As cited

Copy frozen at (site build).

cloud saas

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

GitHub introduced a package firewall for npm that enforces enterprise security policies before packages install on developer systems or in builds. The firewall blocks known malware, critical vulnerabilities, and newly released versions according to an organization's rules. Developers can activate the firewall by redirecting npm traffic through it.

Why it matters: Development teams and build pipeline operators can now prevent risky or unapproved npm packages from entering their systems before installation, reducing supply chain attack surface.

VendorsGitHub
Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

cloud saas

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

GitHub introduced a package firewall for npm that enforces enterprise security policies before packages install on developer systems or in builds. The firewall blocks known malware, critical vulnerabilities, and newly released versions according to an organization's rules. Developers can activate the firewall by redirecting npm traffic through it.

Why it matters: Development teams and build pipeline operators can now prevent risky or unapproved npm packages from entering their systems before installation, reducing supply chain attack surface.

VendorsGitHub
Source published
First seen by Cybersecurity Tracker

Source attribution

Glossary