FAQ-000366 - Code Quality vs Security Vulnerabilities / Unused and Obsolete Code Management

Unused code samples in a package don't affect security, but they can lengthen the review process. To streamline the review and follow secure coding practices, it's best to remove all unused or sample code before submitting your package.

The original answer is technically accurate and covers the key points well. I made minor improvements to enhance readability and conversational tone: shortened 'do not affect' to 'don't affect' for a more natural tone, changed 'align with secure coding practices' to 'follow secure coding practices' for clearer language, replaced 'it is best' with 'it's best' using contractions as recommended in the style guide, and changed 'the package' to 'your package' to write from the user's perspective. No security rules were selected because this FAQ addresses package cleanup and review process efficiency rather than specific security vulnerabilities. The content discusses removing unused code as a best practice for review efficiency, not as a security requirement to prevent vulnerabilities that would be detected by security scanners.