github.com / mathiasbynens
mathiasbynens/ is-potential-custom-element-name
JavaScript·10 files·commit e247786·scanned 18h ago·cached ✓
0/100
SAFE
No malicious patterns found. Repo signals are consistent with a legitimate project.
verdict accurate?
Crypto/Web3 project
threat-state: safelive
FINDINGS ░▒▓
CLEAN
No malicious patterns found across 4/10 content-scanned files.
Static analysis only — treat as “nothing found”, not a guarantee.
Static analysis only — treat as “nothing found”, not a guarantee.
Scores are heuristics. A “safe” verdict means no known-malicious patterns were found — clever malware can look boring. Wrong verdict? Flag it above; confirmed false positives become regression tests.
4 files scanned @ e247786 | 10/29/2026 | heuristic scan — always review manually
risk by category
code execution0
network & exfiltration0
file system access0
obfuscation0
supply chain0
owasp / injection0
telemetry
files 4/10rules hit 0engine v7commit e247786
github
mathiasbynens/is-potential-custom-element-name
Check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard.
9
4
3782d
10 files
4 scanned(40%)
e247786
architecture░▒▓
entry (1) flagged (0) pkg (2)
5 nodes · 3 edgesscroll to zoom · click node to jump to finding