← Back to Scanner

strava Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

strava is an AI agent skill, created by bohdanpodvirnyi and published at openclaw/skills. ClawSecure audited strava across 4 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 4 findings concentrate in Hardcoded Secrets, Policy Violation and Permissions Manifest, including Pattern detected: secret="$STRAVA_CLIENT_SECRET" and Pattern detected: token="$STRAVA_REFRESH_TOKEN". None were rated high or critical severity.

Is strava safe?

ClawSecure audited strava and assigned a security score of 85/100 (Safe), identifying 4 findings across Hardcoded Secrets and Policy Violation. Review the findings below before installing.

What did ClawSecure find in strava?

ClawSecure identified 4 findings in strava, concentrated in Hardcoded Secrets, Policy Violation and Permissions Manifest. The most severe include Pattern detected: secret="$STRAVA_CLIENT_SECRET" and Pattern detected: token="$STRAVA_REFRESH_TOKEN".

How was strava audited?

ClawSecure ran strava through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 4 files from openclaw/skills.

What does a score of 85 mean?

ClawSecure assigned strava a security score of 85/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 4 findings detected are lower-severity. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for strava

ClawSecure detected 4 security findings in strava, spanning Hardcoded Secrets, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for strava

Resolve policy violations
strava trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security StandardsUnderstanding Our 3-Layer Audit ProtocolHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

himalayaScore 85/100uvScore 95/100imsgScore 95/100antigravity-awesome-skillsScore 75/100songseeScore 95/100

Scanned on February 7, 2026. strava is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan