@telemetry-tracker/core@1.5.0
Lightweight telemetry client: events, errors, sessions. Framework-agnostic core.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected entrypoint and supporting modules implement ordinary telemetry behavior without a concrete attack chain. Network hints reflect configured ingest requests, while secret-pattern hints reflect redaction expressions.
Decision evidence
public snapshot- package.json defines build, dev, and test scripts, with no automatic installation lifecycle hooks or runtime self-dependency.
- dist/index.js activates telemetry through init using caller-supplied configuration.
- Telemetry destinations derive from the caller's ingestUrl, and authorization uses the caller's apiKey.
- Network requests post telemetry payloads with the configured authentication headers.
- dist/pii-scrub.js replaces token and API key patterns with redaction placeholders.
Source & flagged code
7 flaggeddist/pii-scrub.js replaces token and API key patterns with redaction placeholders.
dist/pii-scrub.jsView on unpkg · L56package.json defines build, dev, and test scripts, with no automatic installation lifecycle hooks or runtime self-dependency.
Findings
Affected versions and remediation
This report applies to @telemetry-tracker/core@1.5.0.
See all versions of @telemetry-tracker/core for other recorded verdicts.
- Review the evidence and your use of @telemetry-tracker/core@1.5.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.