ClawAudit verdict

pagerduty-agent

88
🟢 Trusted
Low risk — reviewed by ClawAudit, behavior matches stated purpose

PagerDuty incident management using PAGERDUTY_API_KEY to manage the users own PagerDuty account; standard DevOps API wrapper with no suspicious behavior.

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

65
security
100
transparency
100
maintenance

Findings (3)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · API_KEY="your-v2-api-key

Pattern match low

Node http/https module — low-level network access

pagerduty.js · prose · downgraded · require("https")

Pattern match low

Accesses sensitive environment variables

pagerduty.js · prose · downgraded · process.env.PAGERDUTY_API_KEY

Permissions & capabilities

Requires 1 environment variable. (1 sensitive: PAGERDUTY_API_KEY). Requires 1 system binary.

credential_access

Is this flag fair?

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