X509 Certificate Exporter
X509 Certificate Exporter is a Prometheus exporter that reads X.509 certificates and exposes expiration metrics, helping operators detect and renew…
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
74/100 Good
- Maintained
- 100last commit 18 days ago
- Popular
- 60964 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 90no serious findings, 1 minor, CI, tests, OpenSSF Scorecard 8.5/10
Based on 4 of 5 factors.
Availability: platform listings confirmed today
- GitHub stars
- 964
- Open issues
- 14
- Last commit
- 2026-11-03
- Latest release
- v4.2.4
- License
- MIT
- Activity
- rising
Checked 14 days ago - source: GitHub (enix/x509-certificate-exporter)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Install the certificate helper package first Run npm install @peculiar/x509, or yarn add @peculiar/x509, before starting. This gives the exporter the code it needs to read and export certificate files; without it, the app cannot process X.509 certificates. source
- Load the reflect-metadata helper first In your JavaScript, import the reflect-metadata helper (a small add-on that helps the library track object information) before importing @peculiar/x509. Without this early import, the app may fail to start or throw errors when handling certificates. source
- Point Node.js at a known WebCrypto provider If you are running in Node.js, set a WebCrypto-compatible provider (a standard toolkit for secure signing and checking) with x509.cryptoProvider.set(). This helps avoid inconsistent results between machines or versions. source
Fetched 40 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Can I run x509-certificate-exporter without Kubernetes?
It is built for Kubernetes first, but it can also be used as a standalone binary.
What does it integrate with for monitoring?
It is a Prometheus exporter for X.509 certificates.
What should I check if Prometheus reports x509: certificate signed by unknown authority?
That error can be caused by self-signed certificates. You can install the certificate or disable SSL verification.
Is it relevant to self-hosted certificate inventory management?
It is discussed in a guide comparing self-hosted approaches for certificate inventory management.
Answers sourced from github.com, github.com, stackoverflow.com, www.pistack.xyz
Community
- Correctly setup self-signed certificates for your self-hosted ... - Reddit (reddit)
- x509: certificate signed by unknown authority for prometheus (forum)
Collected 48 days ago - public community threads