Configure SECRETS for more advanced safety features

[BeckettFrey]

Configure SECRETS for Advanced Safety Features

Current State

Our security scanning workflow currently uses Safety CLI in basic mode, which works without authentication but has limited capabilities.

Proposed Enhancement

Configure Safety CLI API key to unlock advanced features including:

• Detailed vulnerability reports with remediation guidance
• License compliance checking
• Policy enforcement and custom security rules
• Historical tracking of vulnerability trends
• Priority scoring for vulnerabilities

Implementation Steps

1. Register for a free Safety CLI account at https://safetycli.com
2. Generate an API key from the dashboard
3. Add API key as repository secret: Settings > Secrets > Actions > New repository secret
   • Name: SAFETY_API_KEY
   • Value: <your-api-key>
4. Update workflow to use authenticated mode:

   - name: Check for vulnerabilities with Safety
     env:
       SAFETY_API_KEY: ${{ secrets.SAFETY_API_KEY }}
     run: uv run --only-group security safety scan --json

Benefits

• More comprehensive vulnerability database
• Better false positive filtering
• Detailed fix recommendations

Priority

Low - Current basic scanning is functional; this is an enhancement for better security insights.

Labels

enhancement, security, dependencies