sc-lang-java

Identify Java/Kotlin security anti-patterns and vulnerabilities with CWE mappings.

7|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/fatihkan/badi --skill sc-lang-java-fatihkan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-lang-java
Source: https://github.com/fatihkan/badi/tree/main/.claude/skills/security-check/sc-lang-java
Command: npx skills add https://github.com/fatihkan/badi --skill sc-lang-java-fatihkan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Java/Kotlin-specific security deep scan identifies and surfaces security anti-patterns and vulnerabilities across JVM codebases, enabling faster remediation.

Core Features & Use Cases

  • Detects Java Deserialization gadget chains, JNDI injection patterns (Log4Shell), Spring security misconfigurations, and XML parsing XXE vulnerabilities.
  • Ensures coverage of Kotlin interop risks and the JVM attack surface across source, dependencies, and build configurations.
  • Use Case: Security teams run this scan to generate actionable remediation guidance and CWE mappings for their Java/Kotlin projects.

Quick Start

Run the Java/Kotlin security scan against your codebase and review the results in security-report/architecture.md.

Frequently Asked Questions about sc-lang-java

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan my Java codebase for deserialization and JNDI injection vulnerabilities?

Scanning for Java deserialization and JNDI injection involves identifying gadget chains and Log4Shell patterns across JVM source, build, and dependency surfaces, outputting CWE mappings with actionable remediation guidance.

What is the best way to detect Spring security misconfigurations and XXE vulnerabilities in Kotlin projects?

Detecting Spring security misconfigurations and XML parsing XXE vulnerabilities in Kotlin projects requires checking JVM attack surfaces and Kotlin interop risks against a dedicated security checklist, yielding specific CWE mappings.

Can I use this security scan to check Kotlin interop risks and JVM build configurations?

Yes, you can use this security scan to check Kotlin interop risks and JVM build configurations. It is explicitly designed to cover the full JVM attack surface across source, dependencies, and build files.

How does the Java security checklist identify anti-patterns in my codebase?

The Java security checklist identifies anti-patterns by activating when Java or Kotlin is detected in your architecture report, then scanning for specific JVM vulnerabilities and outputting targeted remediation guidance.

What are common JVM security anti-patterns targeted by deep security checks?

Common JVM security anti-patterns targeted by deep security checks include deserialization gadget chains, JNDI injection patterns, Spring security misconfigurations, XML parsing XXE, and Kotlin interop risks.