Supported languages and analysis scope¶
Offensive360 source analysis includes the language families below. Use the linked guides for practical remediation examples. Available rules, framework handling and file preparation depend on the installed version and enabled analyzers; confirm the scope for your project before treating a scan as complete.
Source-language guides¶
| Language or family | Typical source inputs | Guide |
|---|---|---|
| C# / .NET | .cs, .cshtml, .aspx, related configuration |
C# secure coding |
| Java | .java, related JSP and configuration |
Java secure coding |
| JavaScript | .js, .jsx, .mjs, .cjs |
JavaScript secure coding |
| TypeScript | .ts, .tsx, within the JavaScript analysis family |
TypeScript secure coding |
| Python | .py |
Python secure coding |
| PHP | .php, .phtml, .inc |
PHP secure coding |
| Go | .go |
Go secure coding |
| Ruby | .rb, .ru; additional Rails analyzers vary |
Ruby and Rails |
| Kotlin | .kt, .kts, relevant Android XML |
Kotlin and Android |
| Swift | .swift, relevant plist configuration |
Swift and iOS |
| Objective-C | .m, .mm, relevant headers |
Objective-C secure coding |
| Dart | .dart |
Dart and Flutter |
| C / C++ | .c, .cpp, .cc, .cxx, relevant headers |
C and C++ secure coding |
| Apex | .cls, .trigger |
Apex and Salesforce |
| Oracle Forms / PL/SQL | Readable Forms exports and PL/SQL source | Oracle source review |
Kotlin, Swift, Objective-C, Dart, C/C++, Apex and Oracle source analysis have native analysis paths. Additional AI assistance is a separate capability, with availability and configuration that should be confirmed for the deployment.
Keep analysis types distinct¶
Source analysis examines supplied code and supported configuration. Mobile package analysis examines supported Android or iOS artifacts and can expose different findings. Dependency analysis uses package evidence and advisory data; license and malware checks answer separate questions. Check the actual scan summary rather than inferring these capabilities from a language name.
For Oracle Forms, prepare readable exports and the related PL/SQL units. Direct parsing of binary .fmb or .pll artifacts is not established by this reference. For any language, inspect skipped files, parser failures and analyzer status before concluding that no relevant issues exist.
Additional educational topics¶
The infrastructure as code guide and Rust guide provide secure development examples. Verified product-adapter support is not established here for those guides; request confirmation of the applicable checks.
Start with the language guide index, then connect a finding to its SQL injection, XSS or other weakness article. Examples explain how a fix works; they do not certify every framework, dependency or runtime behavior.