I’m Kyle, the founder of signal.fyi, a tool designed to simplify parent Docker image version management by decoupling it from your existing CI/CD pipeline. Afte

I’m Kyle, the founder of signal.fyi, a tool designed to simplify parent Docker image version management by decoupling it from your existing CI/CD pipeline. After the Log4Shell event while at a fortune 100 company, it was clear there needed to be a better way of keeping parent image versions up to date while also introducing a way to audit these changes over time. Key Features: - Automated Image Syncing: Automatically checks and updates parent Docker images independently of your CI/CD pipeline (1/day|max:3 Dockerfiles/repository). --Capped at 5 repositories (for now) - Improved Efficiency: After installing the Github Marketplace App, each version change is introduced via pull request against your default branch. - SBOM context enrichment: The parent Docker image version (digest;fat manifest) will be available to add in metadata of the SBOM you generate. How It Works: 1. Daily Scans: signal.fyi performs a daily scan to ensure your images are up to date in up to 3 multistage/multi-file Dockerfiles. 2. Notifications: A pull request is opened against your default branch if there is a change from your default branch and/or an existing pull request (open) from a previous day does not already exist. 3. Integration: Easily integrates with existing CI/CD pipelines leveraging pull requests for manual or automated releases. How we handle data: - We treat Github as our database (as much as possible, but we do store some info about you for retrieval purposes). Considering the data we consume from access is out of date pretty much immediately, it makes more sense for use to just query daily when we are working to keep your version (digest;fat manifest) up to date. I’d love to hear your feedback and answer any questions you might have! Thanks, Kyle