dhi.io/ricoberger-script-exporter
Script Exporter
Prometheus exporter to execute scripts and collect metrics from the output or the exit status.
pushed 7 hours ago
linux/amd64, linux/arm64
49.16 MB
for linux/amd64
251
for linux/amd64
Active support
script_exporter, bash, curl, jq, python3, ping, tini
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
-
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About Script Exporter
Script Exporter is a Prometheus exporter that runs the scripts you configure and turns their output or their exit status
into metrics. Prometheus scrapes /probe?script=<name>, the exporter runs that script with the query parameters as
arguments and environment, and reports the script's own metrics together with script_success,
script_duration_seconds and script_exit_code.
This hardened image is built from the official
ricoberger/script_exporter source and ships bash, curl, jq,
python3 and ping for your scripts, as the upstream image does. The Alpine variants also keep upstream's BusyBox tool
set, so existing probe scripts run unchanged there; the Debian variants ship a smaller GNU tool set instead.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
This listing is prepared by Docker. All third-party product names, logos, and trademarks are the property of their respective owners and are used solely for identification. Docker claims no interest in those marks, and no affiliation, sponsorship, or endorsement is implied.