gcfernando/Pipewarden

Detect, install, lint, test, build, and scan your project — locally or in CI.

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stale
License: None

Inputs

name	description	required	default
root	Path to the project root that pipewarden should scan. Defaults to the repository root.	no	.
only	Comma-separated list of stages to run exclusively. All other detected stages will be skipped. Example: "secrets,python" Leave empty to run all detected stages (default behaviour).	no	""
skip	Comma-separated list of stages to skip. Useful when a stage is detected but cannot run in your CI environment (e.g. skip: "docker" when no Docker daemon is available).	no	""
fail-fast	Set to "true" to stop the pipeline immediately after the first stage failure instead of running all stages and reporting at the end.	no	false
sarif-out	File path to write a SARIF 2.1 report to. Pass this path to actions/upload-sarif to surface findings as inline annotations in the GitHub Code Scanning tab and PR diff view. Leave empty to skip SARIF output.	no	""
junit-out	File path to write a JUnit XML report to. Most CI systems (GitHub Actions, Azure DevOps, Jenkins) can parse this format and display per-stage pass/fail results in their test UIs. Leave empty to skip JUnit output.	no	""
diff	Git ref to diff against when running the secrets stage. Only files changed between this ref and HEAD will be scanned, which makes the scan significantly faster on large repositories. Example: "origin/main" Leave empty to scan all files (default behaviour).	no	""
python-version	Python version used to install and run pipewarden itself. This does not need to match the Python version your project targets — pipewarden supports 3.10 and above.	no	3.12
version	Specific pipewarden version to install (e.g. "1.3.0"). Pin this to a release tag in production workflows so a new pipewarden release cannot unexpectedly change your pipeline behaviour. Leave empty to always install the latest published release.	no	""

Outputs

no outputs