clintplay-sdk@0.9.1
Clintplay - Session replay, error tracking, and automatic Playwright test generation
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe default runtime path captures application request credentials and sends them to the package-selected telemetry endpoint without default credential redaction or recipient-specific consent. This is concrete credential disclosure, so the package should be blocked.
Decision evidence
public snapshot- package.json routes package consumers to the inspected `dist/index.js` entrypoint.
- The bundle defaults to the Clintplay API and enables network recording.
- Calling `init()` starts the network recorder when `recordNetwork` is enabled.
- The fetch recorder copies outgoing request headers and bodies, plus text or JSON responses, into network events.
- Only response `set-cookie` is always filtered; request-header and body filtering requires optional sanitization rules.
- The SDK batches events and sends them by POST to its configured API endpoint.
Source & flagged code
7 flagged · loading sourceBrowser source reuses an authenticated session to collect identity data and mutate account settings while reporting externally.
dist/index.jsView on unpkg · L1The bundle defaults to the Clintplay API and enables network recording.
dist/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to clintplay-sdk@0.9.1.
See all versions of clintplay-sdk for other recorded verdicts.
- Avoid installing clintplay-sdk@0.9.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.