ashlr-plugin@1.38.0
Multi-host AI coding efficiency layer for Codex and Claude Code, powered by @ashlr/core-efficiency.
AI Security Review
scanned 1h ago · by lpm-firewall-aiThe package documents telemetry as opt-in and off by default, yet the upgrade-nudge path uploads event metadata whenever a Pro token is available unless a separate kill switch is set. The payload is limited and goes to the package's own service, so this is suspicious undisclosed telemetry rather than data exfiltration.
Decision evidence
public snapshot- The README and telemetry guide describe telemetry as opt-in and off by default.
- The savings status line records an upgrade-nudge event and calls the cloud sync without checking ASHLR_TELEMETRY.
- The sync requires a Pro token, has an ASHLR_STATS_UPLOAD=0 opt-out, and posts events to the configured API, defaulting to api.ashlr.ai.
- Nudge events contain a hashed session ID, bucketed token count, event type, variant, and nudge ID; they do not include prompts or file contents.
- The nudge telemetry is limited to event metadata and bucketed counts.
- The separate audit-upload hook is described as Pro-tier audit logging sent to the Ashlr backend.
Source & flagged code
6 flaggedPackage source references child process execution.
hooks/pulse-emit.tsView on unpkg · L33Package source references dynamic require/import behavior.
hooks/pretooluse-budget-guard.tsView on unpkg · L168Findings
Affected versions and remediation
This report applies to ashlr-plugin@1.38.0.
See all versions of ashlr-plugin for other recorded verdicts.
- Review the evidence and your use of ashlr-plugin@1.38.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.