Security scanning guidance for Israeli web applications covering OWASP Top 10, Israeli Privacy Protection Authority (PPA) compliance, dependency vulnerability scanning, secrets detection, and secure coding patterns for Hebrew/RTL apps.
Trust score 96/100 (Verified) · 86+ installs · 2 GitHub contributors · MIT license
Israeli developers build web applications without dedicated security scanning tools that account for the Israeli context: Hebrew input requiring special sanitization, Unicode bidirectional text attacks, Privacy Protection Law requirements, and leakage of Israeli service API keys. Without tailored scanning, vulnerabilities specific to Israeli applications remain undetected.
npx skills-il add skills-il/security-compliance@v1.1.0-israeli-appsec-scanner --skill israeli-appsec-scanner -a claude-codeRun a full security scan of my application against OWASP Top 10 with focus on Hebrew input and RTL attacks
Scan my project for leaked API keys of Israeli services like Cardcom, Tranzila, and Supabase
Check if my application complies with the Israeli Privacy Protection Law and 2017 security regulations
Scan my codebase for hidden Unicode bidirectional characters that could alter code logic
Added OWASP Top 10 2025 cross-walk note (SSRF folded into A01, new A03 Supply Chain, new A10 Mishandling, A09 renamed to Security Logging and Alerting Failures). Trivy v0.69.4 supply-chain compromise warning. Expanded Amendment 13 breach-notification details (72h window, NIS 100K statutory damages, 100K-individual sensitive-data tier).
Apr 28, 2026
Added Reference Links section (OWASP, PPA, INCD, Trivy, Snyk, TruffleHog). Fixed portability_score.
Apr 15, 2026
Safety protocols per Home Front Command alert type. Covers missiles, hostile aircraft, earthquake, tsunami, hazardous materials, and terrorist infiltration. Includes regional response times, special population guidance, and post-alert exit procedures.
Israeli cybersecurity regulatory framework guidance covering INCD (Ma'arach HaSyber) national directives, Bank of Israel Directive 361 (cyber for financial institutions), Directive 357 (payment security), ISA requirements for TASE-listed companies, and sector-specific rules for fintech and healthtech. Use when user asks about cyber regulation Israel, INCD compliance, Bank of Israel directives, ISA cyber requirements, or sector cyber rules. Do NOT use for privacy law compliance (use israeli-privacy-compliance instead).
Audit and ensure Israeli e-commerce legal compliance, Consumer Protection Law, return policies, price display, accessibility, and cookie consent. Use when user asks about "online store compliance Israel", "Chok Hagnat HaTzarchan", "consumer protection Israel", "return policy Israel", "IS 5568 ecommerce", "cookie consent Israel", or "חוק הגנת הצרכן". Covers cooling-off period validation, price display requirements, Hebrew terms of service generation, accessibility compliance (IS 5568), and business disclosure verification. Do NOT use for food-specific compliance (use israeli-food-business-compliance) or privacy/GDPR (use israeli-privacy-shield).
Want to build your own skill? Try the Skill Creator · Submit a Skill