registry / aislop / 0.15.0

aislop@0.15.0

Catch the slop AI coding agents leave in your code: narrative comments, swallowed exceptions, as-any casts, dead code, oversized functions. 50+ rules across 10 language targets (TypeScript, JavaScript, Expo / React Native, Python, Go, Rust, Ruby, PHP, C#,

AI Security Review

scanned 18d ago · by lpm-firewall-ai

The manifest has no install lifecycle hook, and the flagged agent configuration behavior is reachable through an explicit CLI setup command with agent selection and scope controls. The inspected entry points and adapter code provide no source evidence of credential theft or remote execution.

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

A user runs the hook-install command and chooses the target agent and scope.

Impact

The hooks run aislop during agent file edits; the inspected source does not establish unconsented install-time control of an agent or credential disclosure.

Mechanism

The command adds aislop hooks and guidance to agent configuration files under the selected project or user directory.

AI rationale

Evidence

package.jsondist/cli.jsdist/index.jsdist/mcp.jsdist/core-D4295PVP.js

Decision evidence

public snapshot

AI called this Clean at 88.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json exposes CLI and MCP entry points and lists no install lifecycle hook.
The flagged Claude settings path is scoped to either the project or the user’s home directory.
The hook installer selects agents explicitly or prompts interactively, and exposes project/global scope options.
The package entry point imports local analysis and filesystem modules; no credential forwarding was identified in the inspected source.
The MCP entry point starts a stdio server; no remote gateway behavior was identified in the inspected source.
The framework adapter runs aislop only when its caller sets enabled to true.

Evidence against

The flagged agent configuration change is reachable through the explicit hook-install command; the inspected manifest does not run it during npm installation.
The Claude hook invokes aislop on file edits and updates the scoped settings file and guidance files.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Source & flagged code

6 flagged

dist/core-D4295PVP.jsView file

1import { spawn } from "node:child_process"; L2: import process from "node:process";

High

Child Process

Package source references child process execution.

dist/core-D4295PVP.jsView on unpkg · L1

dist/cli.jsView file

•matchType = previous_version_dangerous_delta matchedPackage = aislop@0.16.0 matchedIdentity = npm:YWlzbG9w:0.16.0 similarity = 0.760 summary = stored previous version shares package body but lacks this dangerous source file

Critical

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

dist/cli.jsView on unpkg

18186}; L18187: const isSafeShellSpawnArray = (content, matchIndex) => /^spawn\s*\(\s*\[/.test(content.slice(matchIndex)) && !/^\s*spawn\s*\(\s*\[\s*["'](?:sh|bash|zsh|cmd|cmd\.exe|powershell|pwsh... L18188: const PLACEHOLDER_EXPR_RE = /^(?:placeholders?|placeholderList|bindMarkers?|bindingMarkers?|bindPlaceholders?|bindingPlaceholders?|parameterPlaceholders?|sqlPlaceholders?)(?:\.\w+\...

Findings

1 Critical5 High3 Medium4 Low

CriticalPrevious Version Dangerous Deltadist/cli.js

HighChild Processdist/core-D4295PVP.js

HighShelldist/cli.js

HighCredential Redirect Persistencedist/index.js

HighRemote Agent Bridgedist/cli.js

HighCross File Remote Execution Contextdist/cli.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to aislop@0.15.0.

See all versions of aislop for other recorded verdicts.

Review the evidence and your use of aislop@0.15.0 before allowing it. Restrict the permissions described in this report.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.

Evidence last updated: 2026-10-17 19:03:34.156Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

registry / aislop / 0.15.0

aislop@0.15.0

AI Security Review

scanned 18d ago · by lpm-firewall-ai

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

A user runs the hook-install command and chooses the target agent and scope.

Impact

The hooks run aislop during agent file edits; the inspected source does not establish unconsented install-time control of an agent or credential disclosure.

Mechanism

The command adds aislop hooks and guidance to agent configuration files under the selected project or user directory.

AI rationale

Evidence

package.jsondist/cli.jsdist/index.jsdist/mcp.jsdist/core-D4295PVP.js

Decision evidence

public snapshot

AI called this Clean at 88.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json exposes CLI and MCP entry points and lists no install lifecycle hook.
The flagged Claude settings path is scoped to either the project or the user’s home directory.
The hook installer selects agents explicitly or prompts interactively, and exposes project/global scope options.
The package entry point imports local analysis and filesystem modules; no credential forwarding was identified in the inspected source.
The MCP entry point starts a stdio server; no remote gateway behavior was identified in the inspected source.
The framework adapter runs aislop only when its caller sets enabled to true.

Evidence against

The flagged agent configuration change is reachable through the explicit hook-install command; the inspected manifest does not run it during npm installation.
The Claude hook invokes aislop on file edits and updates the scoped settings file and guidance files.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Source & flagged code

6 flagged

dist/core-D4295PVP.jsView file

1import { spawn } from "node:child_process"; L2: import process from "node:process";

High

Child Process

Package source references child process execution.

dist/core-D4295PVP.jsView on unpkg · L1

dist/cli.jsView file

Critical

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

dist/cli.jsView on unpkg

Findings

1 Critical5 High3 Medium4 Low

CriticalPrevious Version Dangerous Deltadist/cli.js

HighChild Processdist/core-D4295PVP.js

HighShelldist/cli.js

HighCredential Redirect Persistencedist/index.js

HighRemote Agent Bridgedist/cli.js

HighCross File Remote Execution Contextdist/cli.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to aislop@0.15.0.

See all versions of aislop for other recorded verdicts.

Review the evidence and your use of aislop@0.15.0 before allowing it. Restrict the permissions described in this report.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.

Evidence last updated: 2026-10-17 19:03:34.156Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.