ClawAudit verdict

vikunja-kanban

45
🟠 Risky
Significant concerns — only install if you understand the risks

The skill manages a Vikunja kanban board via API. It requires a long-lived API token which may pose a risk if mishandled.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

80
security
40
transparency
70
maintenance

Findings (1)

Pattern match high

Possible hardcoded credential

scripts/vikunja-add-task.sh · prose · downgraded · TOKEN="${VIKUNJA_TOKEN:?Set VIKUNJA_TOKEN env var}

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class 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