← Back to Scanner

1ly-payments Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

1ly-payments is an AI agent skill, created by 1lystore and published at openclaw/skills. ClawSecure audited 1ly-payments across 2 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 3 findings concentrate in Policy Violation, Permissions Manifest and Code Injection, including Potentially dangerous code pattern detected: base64.*decode and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is 1ly-payments safe?

ClawSecure audited 1ly-payments and assigned a security score of 85/100 (Safe), identifying 3 findings across Policy Violation and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in 1ly-payments?

ClawSecure identified 3 findings in 1ly-payments, concentrated in Policy Violation, Permissions Manifest and Code Injection. 1 was rated high or critical severity. The most severe include Potentially dangerous code pattern detected: base64.*decode and Missing config.json - agent may not be properly configured.

How was 1ly-payments audited?

ClawSecure ran 1ly-payments through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 2 files from openclaw/skills.

What does a score of 85 mean?

ClawSecure assigned 1ly-payments a security score of 85/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status, though 1 finding was rated high or critical and warrants review. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for 1ly-payments

ClawSecure detected 3 security findings in 1ly-payments, spanning Policy Violation, Permissions Manifest and Code Injection.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for 1ly-payments

Resolve policy violations
1ly-payments trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Eliminate dynamic code execution
1ly-payments evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→Understanding Our 3-Layer Audit Protocol→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

stock-market-apiScore 95/100gtsec-smart-stock-selection (1)Score 95/100gtsec-smart-stock-selectionScore 95/100gtsec-smart-stock-selectionScore 95/100skillhubScore 95/100

Scanned on February 18, 2026. 1ly-payments is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan