Files
vectorcraft/sonar-project.properties
Dylan M. Taylor 545671bfa3 ci: lock workflow actions through an actions.lock lockfile
Mutable action tags are a supply-chain risk: a moved tag runs different code
without a diff. Every workflow action is now pinned through
.github/workflows/actions.lock, and CI verifies the lockfile so an out-of-sync
or tampered one fails instead of running.
2026-11-12 07:18:29 -05:00

19 lines
1.2 KiB
Properties

sonar.projectKey=storytold_vectorcraft
sonar.organization=storytold
# S4790 (weak hash): MD5 is the key derivation of the PDF standard security handler revisions 2-4
# (ISO 32000-1 §7.6.3.3), which PDF 1.3-1.6 files use. It is needed to read those files and to write
# the compatibility the user picks, not chosen for new security: the default is 256-bit AES
# (revision 6), which hashes with SHA-2.
sonar.issue.ignore.multicriteria=pdf_md5,gha-lockfile
sonar.issue.ignore.multicriteria.pdf_md5.ruleKey=rust:S4790
sonar.issue.ignore.multicriteria.pdf_md5.resourceKey=crates/pdf/src/encrypt.rs
# githubactions:S7637 asks for every action to be pinned to a commit SHA. A workflow covered by
# .github/workflows/actions.lock runs the commit the lockfile records, so its tag refs are pinned
# and the lockfile covers the actions those actions use too. Sonar does not read lockfiles yet, so
# the rule flags the tag refs anyway:
# https://community.sonarsource.com/t/githubactions-s7637-false-positives-for-actions-pinned-through-native-actions-lock/190814
sonar.issue.ignore.multicriteria.gha-lockfile.ruleKey=githubactions:S7637
sonar.issue.ignore.multicriteria.gha-lockfile.resourceKey=.github/workflows/**