Caveat verdict

xo-protocol

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

Dating trust and identity verification API integration with user-supplied API key and JWT token; all capabilities are consistent with the stated identity verification and profile browsing 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.

48
security
40
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (2)

Pattern match critical

Possible hardcoded credential

README.md · code · apiKey: 'your-api-key

Pattern match low

Accesses sensitive environment variables

examples/mcp-server.js · prose · downgraded · process.env.XO_API_KEY

Permissions & capabilities

No declared permissions — minimal attack surface.

package_installnetwork_incredential_access

Is this flag fair?

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