chore: remove libtropic's pin to develop branch
What changed, and why it matters
This commit removes a single line from the project's Git submodule configuration. It stops pinning the libtropic submodule to the 'develop' branch, meaning the project will now use the submodule's default branch (likely 'main' or 'master'). There is no code change, no bug fix, and no direct security issue visible in the diff itself.
No security action required. Treat as routine repository maintenance. If evaluating supply-chain risk, verify that the default branch of https://github.com/tropicsquare/libtropic.git is a stable, reviewed branch and that submodule updates continue to be pinned to specific commits or tags in the parent repository.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change is in .gitmodules: the ‘branch = develop’ setting for the vendor/libtropic submodule is removed. This is a build/dependency management chore. It does not alter any firmware code, cryptographic logic, or runtime behavior. It changes which upstream Git branch is tracked when the submodule is updated, moving away from a development branch to whatever the repository’s default branch is.
Changed components
.gitmodulesvendor/libtropic submodule configurationInspect captured patch +0 / −1
### .gitmodules
@@ -33,7 +33,6 @@
[submodule "vendor/libtropic"]
path = vendor/libtropic
url = https://github.com/tropicsquare/libtropic.git
- branch = develop
[submodule "vendor/ts-tvl"]
path = vendor/ts-tvl
url = https://github.com/tropicsquare/ts-tvlWhy this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.