autotel-playwright@0.5.17
Playwright fixture for OpenTelemetry: one span per test and trace context injected into API requests
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected runtime behavior matches the package’s Playwright tracing purpose, and the package and selected dependency manifests show no install lifecycle hooks. The network and environment references support configured tracing and do not establish an attack.
Decision evidence
public snapshot- The package manifest points to library entrypoints and declares no lifecycle scripts; it depends on `autotel` 8.4.1.
- The Playwright fixture adds trace headers only to requests matching API origins supplied through environment configuration; other page requests continue without those headers.
- The inspected `autotel` dependency manifest lists build, development, and check scripts, with no install lifecycle hook shown.
- The dependency’s collector stores spans in memory and serializes them when requested; its processor entrypoints expose OpenTelemetry span processors.
Source & flagged code
8 flagged · loading sourceThe package manifest points to library entrypoints and declares no lifecycle scripts; it depends on `autotel` 8.4.1.
package.jsonView on unpkg · L6The package manifest points to library entrypoints and declares no lifecycle scripts; it depends on `autotel` 8.4.1.
.lpm-dependency-evidence-26cad993-c1eb-4915-9214-52e58b7dd824/0/npm-linux/package.jsonView on unpkg · L682Findings
Affected versions and remediation
This report applies to autotel-playwright@0.5.17.
See all versions of autotel-playwright for other recorded verdicts.
- Review the evidence and your use of autotel-playwright@0.5.17 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.