@bigbinary/neeto-playwright-reporter@3.3.3
The custom playwright reporter for neeto-playwright-dashboard.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner findings correspond to an explicit Playwright reporting and sharding workflow, not covert credential theft or install-time execution. Source inspection found no automatic registry-install hook or other concrete malicious behavior.
Decision evidence
public snapshot- The optional CLI posts test-sharding data to the Neeto service using an API key and project key supplied by the user.
- The bundled reporter includes child-process support, while the CLI uses process execution to run Playwright.
- The package has a prepare hook, but it is a development Husky hook rather than an npm install lifecycle hook.
- No preinstall, install, or postinstall hook is present.
- The network call is reached only through the user-invoked neetoplaydash CLI and requires explicit configuration.
- The endpoint and transmitted keys are aligned with the stated Playwright dashboard reporter function.
- No self-dependency, hidden payload download, persistence, or broad project mutation was found.
Source & flagged code
8 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@3.3.3.
See all versions of @bigbinary/neeto-playwright-reporter for other recorded verdicts.
- Review the evidence and your use of @bigbinary/neeto-playwright-reporter@3.3.3 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.