No deprecated API usage warnings
What this checks
Checks for deprecation warnings in OpenClaw security audit output.
Why it matters
Deprecated APIs may be removed in future versions, potentially breaking functionality or exposing security gaps.
How to fix it
This is an experimental informational control. It fires when the security audit detects usage of deprecated OpenClaw APIs that are scheduled for removal in a future release.
Step 1 Get the specifics. The finding's title and detail fields tell you exactly which deprecated API is in use and where:
openclaw security audit --json | jq '.findings[] | select(.checkId | contains("deprecat")) | {title, detail}'Step 2 Update your config or skills. Deprecated APIs typically appear in one of these places:
- Your OpenClaw config file update the flagged key to the new name shown in the finding detail
- A custom skill's SKILL.md update any deprecated tool or command references
- A workflow or agent config replace deprecated action names with their current equivalents
Step 3 Check the changelog for migration instructions if the finding detail doesn't include them:
openclaw changelogStep 4 Restart and verify: openclaw gateway restart, then re-run the audit to confirm the deprecation finding is gone.
Technical details
| Field | Value |
|---|---|
| Control ID | NC-VERS-005 |
| Domain | VERS |
| Severity | Low |
| Status | Experimental |
| Data source | openclaw_security_audit |
| Source type | authoritative |
| Mode | Mode 1 (OpenClaw native) |
| Introduced in | Library v0.1.0 |
False positive notes
Uncertain data source may not produce results on current OpenClaw versions.
Suppress this finding
If this finding is intentional or not applicable to your setup, you can exclude it:
clawvitals exclude NC-VERS-005 reason "your reason here"Exclusions are auditable and expire automatically. See the exclusions guide.