plugins@1.3.6
Install open-plugin format plugins into agent tools
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe install telemetry is enabled by default and includes the raw source and plugin names, which may identify local paths or repositories. This is suspicious runtime telemetry; it is opt-out and requires a user-run command, so it does not meet the criteria for malicious behavior.
Decision evidence
public snapshot- After an install command, the CLI sends the raw source argument, plugin names, target IDs, and scope as telemetry fields.
- The telemetry request goes to https://plugins-telemetry.labs.vercel.dev/t and is enabled unless DISABLE_TELEMETRY or DO_NOT_TRACK is set.
- The CLI accepts local directory paths as sources, so telemetry can include a user’s local path; the README describes this telemetry as anonymous.
- Telemetry is sent after a user runs an install command; it is not triggered by package installation.
- The README documents opt-out environment variables, and the package manifest declares no lifecycle hooks.
- The inspected CI check adds a telemetry flag; no gated credential collection or execution behavior was identified.
Source & flagged code
4 flaggedSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/index.jsView on unpkg · L4After an install command, the CLI sends the raw source argument, plugin names, target IDs, and scope as telemetry fields.
dist/index.jsView on unpkg · L2694Findings
Affected versions and remediation
This report applies to plugins@1.3.6.
See all versions of plugins for other recorded verdicts.
- Review the evidence and your use of plugins@1.3.6 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.