@bigbinary/neeto-playwright-reporter@4.0.4
The custom playwright reporter for neeto-playwright-dashboard.
AI Security Review
scanned 22d ago · by lpm-firewall-aiSource inspection shows the scanner’s shell and network signals arise from normal reporter behavior: fixed Git metadata queries and dashboard reporting. The prepare hook is Husky setup, and no concrete attack surface was established.
Decision evidence
public snapshot- The manifest’s prepare hook runs Husky setup; it declares no preinstall, install, or postinstall hook.
- Both bundles’ shell helper is called with fixed Git queries for commit, author, and branch metadata, which are included in the reporter’s run payload.
- The bundled client defaults to the Neeto Playdash service; its project and API keys come from reporter options or corresponding environment variables.
- The command-line entrypoint requires the Playwright subcommand and forwards the requested arguments to the local Playwright CLI.
- The reporter’s setup runs from Playwright’s reporter lifecycle, and the ESM bundle sends the collected run data through its reporter API.
Source & flagged code
5 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
index.cjs.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @bigbinary/neeto-playwright-reporter@4.0.4.
See all versions of @bigbinary/neeto-playwright-reporter for other recorded verdicts.
- Review the evidence and your use of @bigbinary/neeto-playwright-reporter@4.0.4 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.