pezkuwichain a4e2038aac fix: exclude "account" field from hardcoded-private-key scan (false positive) ...

Every account_overrides.json/chains_for_testBalance.json entry has a
32-byte hex "account" field - a public AccountId32 (Substrate's public
account identifier), not a private key. The two share the same byte
length/hex format, but are fundamentally different: one is meant to be
public (it's literally how you address a chain account), the other
must stay secret. The scanner's regex can't tell them apart and flags
every single one, which just triggered a false "Possible private key
found" failure on PR #33 (the master->main sync).

This isn't a one-off - it'll fire on every future sync PR too, since
chains_for_testBalance.json always has these fields. Left as "FAILURE"
long-term, it trains reviewers to ignore this specific check, which is
exactly the alarm-fatigue failure mode that would let a real leaked
secret slip through unnoticed.

2026-07-08 09:46:58 -07:00

..

auto-merge.yml

Replace force-push sync with PR-based auto-merge workflow

2026-03-02 14:21:07 +03:00

auto-pr.yml

Fix auto-pr to not fail when branches are already in sync

2026-03-02 15:08:14 +03:00

code-quality.yml

ci: add Code Quality and Security workflows (Python lint, JSON validation, chain integrity, secret scan)

2026-02-19 05:56:31 +03:00

security.yml

fix: exclude "account" field from hardcoded-private-key scan (false positive)

2026-07-08 09:46:58 -07:00

sync-nova-base.yml

feat: add Nova-base sync mechanism

2026-02-09 04:39:23 +03:00