← Back to Insights
November 18, 2026 · 5 min read · Dev Security
Open-Source Security Risks in Production
Most modern software is 90%+ open-source dependencies. Your application is built on packages maintained by strangers. Most are safe. Some aren't. Here's what to check, scan, and monitor.
What to check
- SBOM (Software Bill of Materials) — know what packages your software depends on. You can't secure what you haven't inventoried.
- Known vulnerabilities — scan dependencies against CVE databases. If a package you use has a known vulnerability, you need to know.
- Maintainer trust — who maintains the package? One maintainer who abandoned it? A foundation with active maintenance? A compromised npm account?
- License compliance — not security but legal: are you allowed to use this package under your business model?
What to scan
- Dependency scanning — Snyk, Dependabot, GitHub Dependabot alerts. Automated, on every build.
- Container scanning — if you package in Docker, scan the image for vulnerabilities. Trivy, Grype.
- Secret scanning — check that no API keys or credentials are committed in your source or dependencies.
What to monitor
- New vulnerabilities — a package that was safe yesterday may have a CVE today. Continuous monitoring, not one-time scanning.
- Dependency changes — when a maintainer updates a package, verify it didn't introduce a vulnerability or a new malicious dependency.
- Supply chain attacks — watch for compromised packages (npm, PyPI, Docker Hub). If a package you use is compromised, you need to know within hours, not weeks.
Under NIS2, your software supply chain is part of your scope. If a compromised dependency leads to a breach, that's a NIS2 incident. SBOM, scanning, and monitoring are how you manage that risk.
Questions about this?
Get in touch. 15-minute call, no obligation.
Get in touch
Aethel Guard is a Netherlands-based security architecture firm serving EU companies of all sizes. Your architect, not your vendor.