DVC
Git-like version control for ML datasets and pipelines — track experiments, reproduce results, and collaborate on data science projects.
DVC — Data Version Control
DVC brings Git-style version control to machine learning datasets, models, and pipelines. Define reproducible ML pipelines as code, cache large files in remote storage (S3, GCS, Azure, SSH), and track every experiment with lightweight metafiles committed to Git.
Key features
- Data versioning — track large files and directories without bloating your Git repo
- Pipeline DAGs — define stages with
dvc.yaml; DVC caches and only re-runs changed stages - Experiment tracking —
dvc exp run+dvc exp showfor a clean experiment table - Remote storage — S3, GCS, Azure Blob, SSH, HDFS, and local remotes
- CI/CD integration —
dvc reproin GitHub Actions for reproducible ML pipelines - Python API — use programmatically in notebooks or scripts
Quick start
npx ai-supply add dvc-ml-pipeline-versioning
# Or install directly
pip install dvc
# Initialize in a Git repo
git init my-project && cd my-project
dvc init
# Track a dataset
dvc add data/train.csv
git add data/train.csv.dvc .gitignore
git commit -m "Track training data with DVC"
# Define a pipeline stage
dvc run -n train \
-d data/train.csv -d src/train.py \
-o model.pkl \
python src/train.py
# Reproduce the pipeline
dvc repro
Curated mirror of the open-source DVC project (Apache-2.0). Install upstream from the repository.
Compromise signals — malicious or tampered code (leaked secrets, backdoors, a dropped executable) — reduce the score, and known dependency CVEs carry a bounded penalty (they warrant review but never QUARANTINE — update the dependency to clear). Other dangerous-by-capability traits are risk surface, expected for some capabilities. Every finding is mapped to its OWASP control below.
Findings mapped to the OWASP Top 10 for LLM Applications (2025) and the OWASP Machine Learning Security Top 10. Expand any flagged control for the exact findings — compromise reduces the score; expected/risk-surface do not, except a known CVE, which carries a small bounded penalty (high/critical → Review).
The same gate an agent runs before installing (POST /api/v1/trust/dvc-ml-pipeline-versioning/check). Click a policy:
Consume DVC programmatically. Authenticate with an API key or session — see Authorize an agent.
# Agents: CHECK BEFORE YOU INSTALL (no auth) — score, grade, level, capability manifest
curl https://ai-supply.store/api/v1/trust/dvc-ml-pipeline-versioning
# Gate against your org policy (returns { pass, violations })
curl -X POST https://ai-supply.store/api/v1/trust/dvc-ml-pipeline-versioning/check \
-H "Content-Type: application/json" \
-d '{"minGrade":"B","denyPermissions":["shell"],"denyUnknownEgress":true}'
# CLI
npx ai-supply add dvc-ml-pipeline-versioning
# REST (install → download)
curl -X POST https://ai-supply.store/api/v1/listings/dvc-ml-pipeline-versioning/install \
-H "Authorization: Bearer $AIM_KEY"
# MCP tool
install_listing({ "slug": "dvc-ml-pipeline-versioning" })OpenAPI spec →Curated mirror — latest upstream source. See the repository for tagged releases.