security-review

To automate an API security review, trigger an explicit evaluation that identifies permission checks, input validation, and key management gaps in endpoints, outputting findings to a quality.md file for remediation tracking.

The best way to scan web services for hard-coded secrets and unsafe logging is using a checklist-based security evaluation that verifies environment-based key management and safe logging practices, generating a formal assessment.

You perform a dependency audit by triggering a security review that checks dependency hygiene alongside authentication and authorization, documenting any identified gaps to ensure secure deployments.

Yes, this security review relies on explicit activation, meaning it is triggered by a direct path or explicit command to perform the audit, ensuring controlled and targeted evaluations.

This security review applies to web services and APIs across authentication-reliant components, meaning it checks endpoints regardless of the specific framework by evaluating permission checks and key management.

You document security gaps by running the review, which automatically records findings and traceability to a quality.md file, providing an audit trail for tracking remediation.