chore: check in composer.lock for supply chain security#114
Merged
marandaneto merged 2 commits intomasterfrom Mar 31, 2026
Merged
chore: check in composer.lock for supply chain security#114marandaneto merged 2 commits intomasterfrom
marandaneto merged 2 commits intomasterfrom
Conversation
- Remove composer.lock from .gitignore - Add .gitattributes with export-ignore to exclude lock file (and test files) from published package on Packagist The lock file needs to be generated with 'composer install' before merging. Composer verifies package integrity hashes on install, and checking in the lock file pins transitive deps for CI reproducibility.
Generated with composer install. Pins all 30 direct and transitive dependencies with content hashes for integrity verification.
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
2 participants
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.
Problem
composer.lockwas gitignored, so every CI run (composer install) resolved fresh dependencies. If a transitive dependency gets compromised between runs, CI silently pulls the malicious version with no diff to review.CI runs
composer installacross 4 PHP versions (8.2, 8.3, 8.4, 8.5) — all resolving independently without a lock file.Changes
composer.lock(new)composer installcomposer updateand commit the diff.gitignorecomposer.lockfrom gitignore.gitattributes(new)export-ignorerules to exclude files from the Packagist distribution archive:composer.lock— consumers should resolve their own versions/test,/phpunit.xml,/phpcs.xml,/.github,/Makefile— dev/CI files not needed by consumers