Repository navigation
luau-shield v0.2.0: far fewer false positives on real games, with no lost detections.
Tested on a real Roblox game (144 files): all 5 v0.1.0 findings were false positives, and v0.2.0 reports none.
What changed
- Dynamic keys:
for key, value in patch do changed[key] = value endis now tracked field by field, so one untrusted field no longer taints the whole table - Admin guards: code after
isAdmin/hasPermissionchecks on the sender is reported asinfo("admin only"), hidden by default. Guard names are configurable in[guards]. Inline checks (creator id, high group rank, staff role, server-side admin lists) are recognized too - Validators that build a new value (like a
sanitizethat clamps each field) are recognized automatically through function summaries, even beyondmax-call-depth. When that's not possible, the finding suggests declaring them in[[sanitizers]] - Rate limits (luau-shield007): state-machine guards now count as a limit, and work inside a condition is reported as "when a condition holds" instead of "on every request"
%dpatterns now exclude NaN- Faster on large projects (5.7 s → 3.8 s on the largest generated project)
Accuracy
Test corpus grown to 227 vulnerable and 161 safe cases: 292/292 expected findings, 0 false positives, 0 false negatives. Two adversarial review rounds of the fixes found 97 issues (mostly overly permissive guards, like group rank >= 1 counting as admin), each now a regression test.
Known limits
- A guard is trusted by name: an
isAdminthat always returns true is not detected - A wait shorter than 0.1 s does not count as a rate limit
- 11 documented limitation cases (7 false positives, 5 false negatives) in tests/fixtures/limitations
MIT license.