Caveat verdict

m365-planner

m365-planner-v2

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

Microsoft 365 Planner management via Microsoft Graph API using Azure AD app registration with documented required permissions; standard enterprise productivity integration with no unexpected data flows.

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

20
security
70
transparency
100
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 (3)

Pattern match critical

Possible hardcoded credential

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

Pattern match high

Accesses OpenClaw config/secrets directly

SKILL.md · code · ~/.openclaw/.env

Pattern match medium

Popular HTTP library — network access

SKILL.md · code · axios

Permissions & capabilities

No declared permissions — minimal attack surface.

credential_accesspackage_install

Is this flag fair?

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