November 19, 2026
Nobody Installed That Package. So Why Is It Running?
There could be code running inside your application that nobody on your development team remembers choosing.

By Emily Writes
2 min read
Not because someone secretly installed it. Not because a developer made a mistake. It may have arrived through a package the team deliberately added months ago.
Think about it. You install a library to solve one problem. That library relies on another package, which depends on several more. Before long, your application has an entire network of components working behind the scenes.
Your team chose the starting point. But who knows everything that came with it?
This is one of the less visible sides of modern software development. Developers rarely build everything themselves. They use open-source libraries, third-party packages and shared tools because it makes sense to build on work that already exists. It's how teams save time, share knowledge and create increasingly sophisticated applications.
The technical term for those indirectly included components is transitive dependencies****. They're not unusual or inherently unsafe. They're simply part of how software gets assembled.
But their presence raises a question that deserves more attention: how well do we know the people and projects behind the code our applications depend on?
An incident involving a popular JavaScript package called event-stream brought that question into focus in 2018.
Event-stream was used by a large number of software projects. Its original maintainer eventually handed control of the package to another contributor. The new maintainer later introduced a dependency called flatmap-stream, which contained malicious code.
That code was designed to target Copay, a cryptocurrency wallet application. When the affected application was built in the targeted environment, the malicious code could access sensitive wallet information.
Developers using event-stream hadn't necessarily chosen flatmap-stream themselves. It had entered their projects through a package they already relied on.
That's what makes the incident worth remembering. A decision to use one familiar library can introduce components maintained by people the development team may never have encountered.
And software projects don't stand still. Maintainers move on, ownership changes, updates introduce new code and once-active projects can become abandoned. The history of a dependency is not always obvious from its name or version number.
This is why knowing what's inside an application matters. A Software Bill of Materials (SBOM) gives development teams an inventory of the components used in a software product. It helps answer a basic but important question: what are we actually building with?
Dependency analysis can then help identify outdated packages and known vulnerabilities, while software provenance provides information about where components came from and how they entered the development process.
These practices don't make every dependency safe. They make it easier to understand what needs attention.
Teams can also review changes to important packages, monitor maintainer and ownership changes, manage repository permissions and protect their build pipelines. Security assessments can examine these development environments and third-party integrations alongside the finished application.
None of this is an argument against open-source software. Its collaborative nature is one of the reasons modern development has progressed so quickly. A huge amount of useful technology exists because developers have been willing to share their work.
But collaboration also means relying on code created and maintained beyond your own team.
And perhaps that's the part worth thinking about. We spend time reviewing the features we build, the applications we deploy and the tools we purchase. Yet some of the most important components in those applications may be several layers removed from the original decision.
Your developers may know exactly what they added to the application. But do they know everything that came along with it?