Caveat verdict

office365-connector

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

Microsoft 365 connector using OAuth/Microsoft Graph API to read the user email, calendar, and contacts; credential_access is for the user own M365 token.

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

40
security
50
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (4)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · SECRET="your-client-secret

Pattern match medium

Accesses OpenClaw config/secrets directly

references/setup-guide.md · prose · downgraded · ~/.openclaw/openclaw.json

Pattern match low

Accesses sensitive environment variables

accounts.js · prose · downgraded · process.env.AZURE_CLIENT_SECRET

Pattern match low

Node http/https module — low-level network access

auth.js · prose · downgraded · require('https')

Permissions & capabilities

No declared permissions — minimal attack surface.

credential_access

Is this flag fair?

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