aist-project-profile-analyzer

You can reduce false positives in SAST by applying deterministic path exclusion patterns to filter out non-production folders like tests, docs, and build artifacts from cloned repositories, sharpening scan focus on production code.

Path exclusion for SAST repository analysis is the process of identifying and filtering out non-production directories. It generates deterministic, machine-readable patterns that tell the scanner which paths to skip, reducing noise across diverse project layouts.

You generate broad-coverage path exclusion patterns by analyzing a cloned project repository to distinguish production versus non-production folders, producing deterministic, machine-readable patterns for diverse project layouts and languages.

Yes, you can use the generated exclusion patterns in continuous scanning workflows. The analyzer produces deterministic, machine-readable patterns designed for the AIST project profile, supporting integration to improve scan precision continuously.

Yes, the path exclusion analyzer supports multiple programming languages. It is designed to apply to diverse project layouts and languages, producing broad-coverage exclusion patterns for typical non-production folders regardless of the tech stack.