@testrelic/playwright-analytics@2.12.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 install-time mutation is limited to the package's own configuration and includes skip conditions; the reviewed reporter and CLI behavior fits analytics and report viewing. Scanner similarity and exfiltration hints are not supported as malicious behavior by the inspected source.
Decision evidence
public snapshot- The postinstall hook is scoped to the installation project, skips CI and nested installs, and creates a package-specific configuration file only when it is absent.
- The reporter uploads test-run data to the configured TestRelic service; inspected upload code does not establish command-output exfiltration.
- The CLI child-process call opens a report in the platform browser using an argument array.
- The fixture entrypoints load Playwright and package support code; no attack behavior was established from the reviewed entrypoints.
- Installation automatically writes a TestRelic configuration file in the consumer project when the hook's skip conditions do not apply.
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.12.1.
See all versions of @testrelic/playwright-analytics for other recorded verdicts.
- Review the evidence and your use of @testrelic/playwright-analytics@2.12.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.