Repository navigation
Send weekly inventory snapshots and daily CVE results - #3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recense currently emits every package on every daily scan. Send a full package snapshot when each host or container is first seen, then weekly. Continue rebuilding inventory and checking all packages for CVEs daily, emitting individual findings and severity summaries. Add fix-availability fields for SigNoz filtering.
Persist only emission timestamps in a disposable, atomically replaced schedule file. Missing or corrupt state triggers full snapshots; state-write failures do not prevent CVE checks. Pod replacement resets the schedule. This reduces inventory log traffic, not scanner resource use, and does not add delivery guarantees.
Also exclude
/mnt/k8s-disks, where EKS nodeadm stores containerd and kubelet backing directories. Without this exclusion, Syft can scan those files through their backing paths despite canonical-path exclusions. Preserve software under other/mntpaths.Release/chart version: 0.2.1. The AWS canary remains on 0.2.0 until release approval.
Validation:
/mntpositive control.