dirty-waters 0.26.0

Automatically detect software supply chain smells and issues

dirty-waters

Dirty-waters automatically finds software supply chain issues in software projects by analyzing the available metadata of all dependencies, transitively.

Reference: Dirty-Waters: Detecting Software Supply Chain Smells, Technical report 2410.16049, arXiv, 2024.

By using dirty-waters, you identify the shady areas of your supply chain, which would be natural target for attackers to exploit.

Kinds of problems identified by dirty-waters:

• Dependencies with no link to source code repositories (high severity)
• Dependencies with no tag / commit sha for release, impossible to have reproducible builds (high severity)
• Deprecated Dependencies (medium severity)
• Depends on a fork (medium severity)
• Dependencies with no build attestation (low severity)

Additionally, dirty-waters gives a supplier view on the dependency trees (who owns the different dependencies?)

dirty-waters is developed as part of the Chains research project.

Installation

To set up dirty-waters, follow these steps:

1. Clone the repository:

git clone https://github.com/chains-project/dirty-waters.git
cd dirty-waters

2. Set up a virtual environment and install dependencies:

python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
cd tool

In alternative to virtual environments, you may also use the Nix flake present in this repository.

3. Set up the GitHub API token (ideally, in a .env file):

export GITHUB_API_TOKEN=<your_token>

Usage

Run the tool using the following command structure:

Arguments:

usage: main.py [-h] -p PROJECT_REPO_NAME -v RELEASE_VERSION_OLD [-vn RELEASE_VERSION_NEW] -s [-d] [-n] -pm {yarn-classic,yarn-berry,pnpm,npm,maven} [--pnpm-scope]

options:
  -h, --help            show this help message and exit
  -p PROJECT_REPO_NAME, --project-repo-name PROJECT_REPO_NAME
                        Specify the project repository name. Example: MetaMask/metamask-extension
  -v RELEASE_VERSION_OLD, --release-version-old RELEASE_VERSION_OLD
                        The old release tag of the project repository. Example: v10.0.0
  -vn RELEASE_VERSION_NEW, --release-version-new RELEASE_VERSION_NEW
                        The new release version of the project repository.
  -s, --static-analysis
                        Run static analysis and generate a markdown report of the project
  -d, --differential-analysis
                        Run differential analysis and generate a markdown report of the project
  -n, --name-match      Compare the package names with the name in the in the package.json file. This option will slow down the execution time due to the API rate limit of
                        code search.
  -pm {yarn-classic,yarn-berry,pnpm,npm,maven}, --package-manager {yarn-classic,yarn-berry,pnpm,npm,maven}
                        The package manager used in the project.
  --pnpm-scope          Extract dependencies from pnpm with a specific scope using 'pnpm list --filter <scope> --depth Infinity' command. Configure the scope in tool_config.py
                        file.

Example usage:

1. Static analysis:

python3 main.py -p MetaMask/metamask-extension -v v11.11.0 -s -pm yarn-berry

• Example output: Static Analysis Report Example

2. Differential analysis:

python3 main.py -p MetaMask/metamask-extension -v v11.11.0 -vn v11.12.0 -s -d -pm yarn-berry

• Example output: Differential Analysis Report Example

Notes:

• -v should be the version of GitHub release, e.g. for this release, the value should be v11.11.0, not Version 11.11.0 or 11.11.0.
• The -s flag is required for all analyses.
• When using -d for differential analysis, both -v and -vn must be specified.

Software Supply Chain Smell Support

dirty-waters currently supports package managers within the JavaScript and Java ecosystems. However, due to some constraints associated with the nature of the package managers, the tool may not be able to detect all the smells in the project. The following table shows the supported package managers and their associated smells:

Package Manager	No Source Code Repository	Invalid Source Code Repository URL	No Release Tag	Deprecated Dependency	Depends on a Fork	No Build Attestation
Yarn Classic	Yes	Yes	Yes	Yes	Yes	Yes
Yarn Berry	Yes	Yes	Yes	Yes	Yes	Yes
Pnpm	Yes	Yes	Yes	Yes	Yes	Yes
Npm	Yes	Yes	Yes	Yes	Yes	Yes
Maven	Yes	Yes	Yes	No	Yes	No

Notes

Inaccessible Tags

Sometimes, the release version specified in a lockfile/pom/similar is not necessarily the same as the tag used in the repository. This can happen for a variety of reasons. We have compiled several tag formats which were deemed reasonable to lookup, if the exact tag specified in the lockfile/pom/similar is not found. They come from a combination of AROMA's work and our own research on this subject. These formats are the following:

• <tag>
• v<tag>
• r-<tag>
• release-<tag>
• parent-<tag>
• <package_name>@<tag>
• <package_name>-v<tag>
• <package_name>_v<tag>
• <package_name>-<tag>
• <package_name>_<tag>
• release/<tag>
• <tag>-release
• v.<tag>
• p1-p2-p3<tag>

Note than this does not mean that if dirty-waters does not find a tag, it doesn't exist: it means that it either doesn't exist, or that its format is not one of the above.

This list may be expanded in the future. If you feel that a relevant format is missing, please open an issue and/or a pull request!

Academic Work

• Dirty-Waters: Detecting Software Supply Chain Smells

Other issues not handled by dirty-waters

• Missing dependencies: simply run mvn/pip/... install :)
• Bloated dependencies: we recommend DepClean for Java, depcheck for NPM
• Version constraint inconsistencies: we recommend pipdeptree for Python

License

MIT License.