nexgenr@1.1.1
NexgenR — terminal AI coding agent
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI enables vendor telemetry unless configuration explicitly disables it, and the included README does not disclose this behavior. The observed context is ordinary product metadata sent to NexgenR's own host, so this merits a warning rather than a block.
Decision evidence
public snapshot- CLI telemetry is enabled unless the user's configuration explicitly sets `telemetry` to false; it includes a device ID, session ID, model, and uses a cached NexgenR access token.
- Telemetry context includes app and core versions, runtime, platform, architecture, Node and OS versions, CI status, locale, terminal, and UI mode.
- The configured telemetry endpoint is on NexgenR's own `ia.nexgen.systems` host.
- The package's executable entrypoint is `dist/main.mjs`, and the bundle invokes its CLI startup function.
- The observed telemetry context consists of ordinary product and runtime metadata; no credential theft or unrelated collector was identified.
- The manifest declares no install lifecycle hooks.
- The included README search found no telemetry mention, though the configuration provides an opt-out.
Source & flagged code
4 flaggedPackage contains source files above the normal full-analysis size ceiling.
dist/main.mjsView on unpkgPackage contains an oversized executable-looking CLI entrypoint.
dist/main.mjsView on unpkgCLI telemetry is enabled unless the user's configuration explicitly sets `telemetry` to false; it includes a device ID, session ID, model, and uses a cached NexgenR access token.
dist/main.mjsView on unpkg · L3213Findings
Affected versions and remediation
This report applies to nexgenr@1.1.1.
See all versions of nexgenr for other recorded verdicts.
- Review the evidence and your use of nexgenr@1.1.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.