← Back to Scanner

niri-ipc Security Audit Report

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

niri-ipc is an AI agent skill, created by atefr and published at openclaw/skills. ClawSecure audited niri-ipc across 6 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, Resource Abuse and Permissions Manifest, including Pattern detected: while True: and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is niri-ipc safe?

ClawSecure audited niri-ipc and assigned a security score of 85/100 (Safe), identifying 3 findings across Policy Violation and Resource Abuse. Review the findings below before installing.

What did ClawSecure find in niri-ipc?

ClawSecure identified 3 findings in niri-ipc, concentrated in Policy Violation, Resource Abuse and Permissions Manifest. 1 was rated high or critical severity. The most severe include Pattern detected: while True: and Missing config.json - agent may not be properly configured.

How was niri-ipc audited?

ClawSecure ran niri-ipc through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 6 files from openclaw/skills.

What does a score of 85 mean?

ClawSecure assigned niri-ipc 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 niri-ipc

ClawSecure detected 3 security findings in niri-ipc, spanning Policy Violation, Resource Abuse and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for niri-ipc

Resolve policy violations
niri-ipc 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.
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 StandardsUnderstanding Our 3-Layer Audit ProtocolHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

sonoscliScore 95/100f968405e77f5edd5Score 95/100wacliScore 95/100a6fe8825e22682daScore 95/100cbc3dac9d0cccf41Score 95/100

Scanned on February 7, 2026. niri-ipc 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