Skip to content

fix(ci): scan TLA+ specs (.tla) as text, not as disguised payloads - #213

Merged
afeezorobsco-cyber merged 1 commit into
mainfrom
fix/scanner-tla-extension
Oct 21, 2026
Merged

afeezorobsco-cyber merged 1 commit into
mainfrom
fix/scanner-tla-extension

Conversation

@afeezorobsco-cyber

Copy link
Copy Markdown
Contributor

Follow-up to the .vue fix (core #212, escrow #220, web #196). docforum-escrow #225 adds a TLA+ formal specification (spec/Escrow.tla). The malware scan flagged it HIGH as disguised-code, because .tla wasn't on the code/text extension list, so its required check was blocked. I reviewed the spec by hand: it's a normal TLA+ model of the escrow lifecycle, and its README links to the official TLA+ tools release.

Change: add tla to the scanner's text-extension list. Every line rule still runs on these files.

Tested with the scanner harness:

🤖 Generated with Claude Code

A TLA+ spec in docforum-escrow #225 was flagged HIGH by the
disguised-code rule because .tla wasn't a known text extension. Every
line rule still runs on .tla files.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@afeezorobsco-cyber
afeezorobsco-cyber merged commit a0734df into main Oct 21, 2026
2 checks passed
@afeezorobsco-cyber
afeezorobsco-cyber deleted the fix/scanner-tla-extension branch October 21, 2026 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant