Caveat verdict

gleap

berthelol-gleap

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

Gleap support analytics integration sending declared credentials only to api.gleap.io for ticket data retrieval.

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

55
security
50
transparency
70
maintenance

Findings (2)

Pattern match critical

Possible hardcoded credential

references/use-cases.md ยท code ยท TOKEN="your-token-here

Pattern match medium

References webhook/callback URL

references/use-cases.md ยท code ยท WEBHOOK_URL

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

Requires 2 environment variables. (1 sensitive: GLEAP_TOKEN). Requires 2 system binaries. (1 elevated: curl).

credential_accessnetwork_outnetwork_in

Is this flag fair?

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