Exclude Gemfile.lock from gem package to avoid false positive security alerts #70
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.
Summary
Exclude
Gemfile.lockfrom the gem package to prevent false positive vulnerability alerts from security scanners like Amazon Inspector.Problem
Security scanners (e.g., Amazon ECR Enhanced Scanning, Amazon Inspector) scan all files in container images, including
Gemfile.lockfiles inside gem packages. The developmentGemfile.lockin this gem references older versions of dependencies (e.g.,actionpack 7.0.4), which triggers vulnerability alerts even though applications using this gem typically have newer, patched versions.Reference: https://tech.medpeer.co.jp/entry/ecr-enhanced-scanning-false-positive
Solution
Exclude
Gemfile.lockfromspec.filesin the gemspec, as it's only used during gem development and not needed at runtime.