registry / Telemetry / @ricsam/r5d-browser / 0.0.195-prod.1793289531781.gefd293209f2c4044ce85479fc2ef81ecf26895b2
@ricsam/r5d-browser@0.0.195-prod.1793289531781.gefd293209f2c4044ce85479fc2ef81ecf26895b2
`r5d-browser start` updates the client automatically. It checks the authenticated environment's selected release once a minute and stages verified packages privately using npm. After the current action finishes, it reconnects a new CLI process to the same
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe CLI enables Sentry error reporting by default, and the README does not disclose telemetry. Its configuration disables default PII and applies a sanitizer, so this is a warning-level telemetry concern rather than evidence of malicious collection.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running `r5d-browser auth` or starting the browser CLI.
Impact
Error events may be sent to the configured Sentry endpoint without the package documenting telemetry in its README.
Mechanism
The CLI discovers a Sentry configuration from the selected server or environment and initializes Sentry error reporting with a sanitization hook.
AI rationale
The CLI enables Sentry error reporting by default, and the README does not disclose telemetry. Its configuration disables default PII and applies a sanitizer, so this is a warning-level telemetry concern rather than evidence of malicious collection.
Evidence
dist/mjs/main.mjs.lpm-dependency-evidence-6a6a47f2-e190-4769-a3b6-06071ca13d81/0/npm-linux/dist/mjs/telemetry-node.mjs
Network endpoints1
Sentry endpoint from server-discovered configuration or SENTRY_DSN; exact host is configurable