setup-leanx
Audited by Snyk on Nov 16, 2026
HIGH W008: Secret detected in skill content (API keys, tokens, passwords).
- Secret detected (high risk: 1.00). The potential_matches list is empty, but the content still needs review. references/leanx-api.md lines 28-31 contain a "Public sandbox credential": a Merchant ID, UUID, 128-hex Hash Key, and an Auth Token with a 128-hex secret segment. These are high-entropy literal values that look like real credentials.
The document says this credential is publicly published on LeanX's official Credential page for generic sandbox connectivity tests. It only reaches the sandbox environment and returns generic mock responses. That makes it a vendor-published demo credential, not a private leaked one.
Even so, it is a literal, working-format, high-entropy Hash Key and Auth Token embedded in the skill, and the entropy rules say to flag those. Nothing about the values marks them as placeholders: they are not truncated, not redacted, and not obviously fake. A scanner or reviewer would treat them as real credentials, so I am flagging them, while noting that the sandbox-only, publicly documented context lowers the severity.
The other items are not secrets. The env var templates use <AUTH_TOKEN>-style placeholders. The payout test accounts 1111111111 and 1212121212 are low-entropy test values. The Google Drive links are download URLs.
MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).
- Direct money access detected (medium risk: 0.30). The skill is a LeanX payment-gateway integration guide. Its workflow documents creating real bills through
create-bill-pageandcreate-bill-silent(indirect operations, SKILL.md:20-25, 36) and payouts throughcreate-payout-invoicefrom a prefund pool, which moves money (direct, SKILL.md:46). Much of the content is development guidance, which would be excluded, but the skill also describes operating the bill and payout routes, so under the recall-first override it is treated as in scope. For the direct payout route, the control is the documentedauth-tokenmerchant credential, which LeanX validates on every API call (SKILL.md:34, 44 with error 5688 Invalid Token). That is service-enforced authentication, so the direct route is not high-severity. Medium is assigned because an indirect bill-creation operation and a direct payout route with established authentication are both present.
Issues (2)
Secret detected in skill content (API keys, tokens, passwords).
Direct money access capability detected (payment gateways, crypto, banking).