> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/oss-supply-chain-security/introduction.md).

# Introduction

Open-source supply chain attacks target the software dependencies your applications and CI/CD pipelines rely on. These attacks often use newly published packages, compromised maintainer accounts, or malicious install scripts to steal secrets, execute arbitrary code, or pivot deeper into your infrastructure.

Examples of such attacks include:

{% embed url="<https://www.stepsecurity.io/blog/sha1-hulud-the-second-coming-zapier-ens-domains-and-other-prominent-npm-packages-compromised>" %}

{% embed url="<https://www.stepsecurity.io/blog/supply-chain-security-alert-popular-nx-build-system-package-compromised-with-data-stealing-malware>" %}

{% embed url="<https://www.stepsecurity.io/blog/20-popular-npm-packages-compromised-chalk-debug-strip-ansi-color-convert-wrap-ansi>" %}

{% embed url="<https://www.stepsecurity.io/blog/ghostaction-campaign-over-3-000-secrets-stolen-through-malicious-github-workflows>" %}

The OSS Supply Chain Security capabilities in StepSecurity cover dependencies from the **npm** and **PyPI** ecosystems, with a layered model built around three pillars:

Prevent – stop high risk dependencies and behaviors before they are introduced

Detect – continuously identify compromised packages and suspicious changes across your codebase

Respond – investigate incidents quickly and assess organization wide impact


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stepsecurity.io/oss-supply-chain-security/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.