Caveat verdict

api-security-best-practices

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

A security best practices guide covering JWT authentication, input validation, rate limiting, and data protection for API design; purely educational with no suspicious behavior.

⚠ 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.

75
security
90
transparency
70
maintenance

Findings (3)

Pattern match high

Possible hardcoded credential

SKILL.md · prose · downgraded · SECRET = 'my-secret-key

Pattern match low

Opens WebSocket connection

SKILL.md · prose · downgraded · WebSocket

Pattern match low

Accesses sensitive environment variables

SKILL.md · prose · downgraded · process.env.JWT_SECRET

Permissions & capabilities

No declared permissions — minimal attack surface.

Is this flag fair?

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