
Josh Dolitski developed automated vulnerability data workflows and a scanner audit CLI tool for the chainguard-dev/vulnerability-scanner-support repository. He implemented CI/CD pipelines using GitHub Actions and shell scripting to regenerate and normalize vulnerability data, ensuring consistent and up-to-date answers for test cases. Leveraging Go, Docker, and tools like Melange and Apko, Josh built a CLI utility to validate vulnerability scanners against Chainguard’s official test images, producing HTML reports for expected versus actual CVE results. His work improved data quality, reproducibility, and security posture, while embedding documentation and automation to streamline onboarding and quality assurance across development teams.
June 2025: Delivered a new scanner-audit CLI tool and data provisioning pipelines in vulnerability-scanner-support, enabling automated validation of vulnerability scanners against Chainguard's official test cases, with reproducible test images, HTML reporting, CI workflow, and refreshed test data. These efforts improve QA reliability, speed, and collaboration across teams, and demonstrate strong Go development, DevSecOps tooling, and test data management.
June 2025: Delivered a new scanner-audit CLI tool and data provisioning pipelines in vulnerability-scanner-support, enabling automated validation of vulnerability scanners against Chainguard's official test cases, with reproducible test images, HTML reporting, CI workflow, and refreshed test data. These efforts improve QA reliability, speed, and collaboration across teams, and demonstrate strong Go development, DevSecOps tooling, and test data management.
February 2025 focused on delivering Chainguard-tailored support within the vulnerability-scanner-support repo, establishing automated data generation workflows and expanding CI/CD coverage to ensure end-to-end consistency for Chainguard data. The work aligns with the goal of faster remediation cycles and higher data fidelity for Chainguard users.
February 2025 focused on delivering Chainguard-tailored support within the vulnerability-scanner-support repo, establishing automated data generation workflows and expanding CI/CD coverage to ensure end-to-end consistency for Chainguard data. The work aligns with the goal of faster remediation cycles and higher data fidelity for Chainguard users.
January 2025 – chainguard-dev/vulnerability-scanner-support Key features delivered: - Automated vulnerability data regeneration and CI/CD workflow: introduced an automated process to regenerate answers.json using grype and wolfictl, format the output with jq, and integrate this flow into GitHub Actions for scheduled regeneration, including PR-based updates, proper permissions, and token handling. - Answers data sorting and normalization: added a script to sort and normalize vulnerability data within data/answers.json to ensure consistent ordering across test cases, improving data quality and comparability. Major bugs fixed: - Fixed path to octo-sts trust policy to ensure deployments and scans use the correct policy configuration. - Improved token plumbing for the regeneration workflow, enhancing security and reliability of CI-triggered operations. Overall impact and accomplishments: - Automation reduces manual data maintenance and ensures up-to-date vulnerability data, accelerating vulnerability reporting and improving CI reliability. - Standardized data ordering enhances test reproducibility and cross-environment comparisons, reducing false diffs. - Security posture improved through proper token handling and policy path fixes. Technologies/skills demonstrated: - Grype, Wolfi, jq, GitHub Actions, cron scheduling, scripting, token handling, policy path remediation, and data normalization.
January 2025 – chainguard-dev/vulnerability-scanner-support Key features delivered: - Automated vulnerability data regeneration and CI/CD workflow: introduced an automated process to regenerate answers.json using grype and wolfictl, format the output with jq, and integrate this flow into GitHub Actions for scheduled regeneration, including PR-based updates, proper permissions, and token handling. - Answers data sorting and normalization: added a script to sort and normalize vulnerability data within data/answers.json to ensure consistent ordering across test cases, improving data quality and comparability. Major bugs fixed: - Fixed path to octo-sts trust policy to ensure deployments and scans use the correct policy configuration. - Improved token plumbing for the regeneration workflow, enhancing security and reliability of CI-triggered operations. Overall impact and accomplishments: - Automation reduces manual data maintenance and ensures up-to-date vulnerability data, accelerating vulnerability reporting and improving CI reliability. - Standardized data ordering enhances test reproducibility and cross-environment comparisons, reducing false diffs. - Security posture improved through proper token handling and policy path fixes. Technologies/skills demonstrated: - Grype, Wolfi, jq, GitHub Actions, cron scheduling, scripting, token handling, policy path remediation, and data normalization.

Overview of all repositories you've contributed to across your timeline