ClawAudit verdict

youtube-apify-transcript

88
🟢 Trusted
Low risk — reviewed by ClawAudit, behavior matches stated purpose

YouTube transcript fetcher via declared Apify API using user-supplied APIFY_API_TOKEN; local caching is transparent and no unauthorized forwarding present.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

35
security
90
transparency
100
maintenance

Permission integrity

Performs file operations but does not declare file-accessing binaries

file_read+write

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (3)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · TOKEN="apify_api_YOUR_TOKEN_HERE

Pattern match high

Accesses shell history/config

SKILL.md · code · ~/.zshrc

Pattern match low

Python os.environ.get — reads environment variable

scripts/fetch_transcript.py · prose · downgraded · os.environ.get(

Permissions & capabilities

Requires 1 system binary.

file_writepackage_install

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API