@testrelic/playwright-analytics@2.13.1
Playwright test analytics reporter with E2E navigation tracking, API call capture, network stats, failure diagnostics, and interactive HTML reports
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe lifecycle hook has CI, nested-install, and existing-file guards and writes only the package's own configuration. The command-output signal corresponds to Git metadata collection in the reporter, while cloud reporting requires a configured API key and uses the package's TestRelic endpoint.
Decision evidence
public snapshot- The install hook creates only an idempotent, package-specific TestRelic configuration file and skips when the file already exists.
- Cloud initialization falls back to local mode when no API key is configured.
- The reporter's Git commands collect branch and commit metadata for analytics reporting.
- The API fixture's default capture configuration redacts common credential headers and body fields.
Source & flagged code
11 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @testrelic/playwright-analytics@2.13.1.
See all versions of @testrelic/playwright-analytics for other recorded verdicts.
- Review the evidence and your use of @testrelic/playwright-analytics@2.13.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.