Caveat verdict

x-oauth-api

88
๐ŸŸข Trusted
No high-risk patterns surfaced by the deep scan โ€” automated capability review, not behavioral proof.

Official X API v2 client for posting tweets using OAuth 1.0a credentials in env vars; calls go only to api.twitter.com, behavior matches stated posting purpose.

โš  Flagged for review โ€” coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

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

68
security
80
transparency
80
maintenance

Findings (2)

Pattern match critical

Possible hardcoded credential

README.md ยท code ยท API_KEY="your_consumer_key

Pattern match low

Accesses sensitive environment variables

bin/x.js ยท prose ยท downgraded ยท process.env.X_API_KEY

Permissions & capabilities

Requires 4 environment variables. (4 sensitive: X_API_KEY, X_API_SECRET, X_ACCESS_TOKEN, X_ACCESS_TOKEN_SECRET).

credential_access

Is this flag fair?

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