Caveat verdict

outlook

outlook-365

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

Microsoft Outlook management via Graph API using OAuth2; credentials stored in user-configured directory and used only for accessing the users own Outlook account.

โš  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.

60
security
80
transparency
90
maintenance

Findings (2)

Pattern match critical

Possible hardcoded credential

references/setup.md ยท code ยท SECRET="your-client-secret

Pattern match medium

References sudo โ€” requests elevated privileges

references/setup.md ยท prose ยท downgraded ยท sudo

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class A/B). Final tier capped at Caution โ€” cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

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