aislop@0.19.1
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 6d ago · by lpm-firewall-aiThe flagged credential flow is not present: provider credentials remain with the selected local provider, and the package's observed telemetry goes to PostHog with an opt-out. The manifest has no install hook, and the remote-agent capability is tied to an explicit CLI command.
Decision evidence
public snapshot- The manifest exposes the CLI and library but declares no install lifecycle hook.
- The agent feature is described as a user-invoked command; it launches the selected local provider and passes it the existing environment.
- CLI telemetry sends an anonymous install ID and allowlisted usage data to PostHog, and can be disabled by environment variables or configuration.
- The README links to telemetry documentation; no credential redirection to an unrelated host was found.
- Runtime telemetry is enabled by default outside CI and includes command and aggregate usage metrics.
- The CLI can launch coding-agent providers with the user's environment when the agent feature is used.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/core-D4295PVP.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to aislop@0.19.1.
See all versions of aislop for other recorded verdicts.
- Review the evidence and your use of aislop@0.19.1 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.