chore: remove example/ios/Podfile.lock from version control#206
Merged
robert-northmind merged 1 commit intomainfrom Apr 10, 2026
Merged
Conversation
The Flutter engine CocoaPod always reports version 1.0.0 regardless of the actual Flutter SDK version, triggering a false-positive CVE-2022-3095 (Critical) in vulnerability scanners. The file is auto-generated by Flutter's build tooling and adds no reproducibility value for the example app. Made-with: Cursor
robert-northmind
deleted the
chore/remove-podfile-lock-false-positive-cve
branch
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
1 participant
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
example/ios/Podfile.lockfrom git tracking and add it to.gitignore1.0.0in its podspec, causing Grype to flag CVE-2022-3095 (Critical, 9.8) as a false positive — the actual Flutter SDK in use is 3.41.2, well past the fix version of 3.3.3pod installruns automatically duringflutter build ios) and all pods except PLCrashReporter are local path-based sourcesTest plan
example/ios/Podfile.lockis no longer trackedcd example && flutter build ios --no-codesignMade with Cursor
Note
Low Risk
Low risk housekeeping change that only updates repo hygiene by ignoring and removing an auto-generated lockfile; no runtime code paths are affected.
Overview
Removes
example/ios/Podfile.lockfrom version control and adds it to.gitignoreso the example app’s generated CocoaPods lockfile is no longer tracked.This reduces noise/false-positive dependency scanning caused by the Flutter engine pod reporting version
1.0.0.Reviewed by Cursor Bugbot for commit 9c68619. Bugbot is set up for automated code reviews on this repo. Configure here.