@bigbinary/neeto-playwright-reporter@3.4.1
The custom playwright reporter for neeto-playwright-dashboard.
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe flagged credential and network behavior is part of the reporter’s configured API workflow: the CLI supplies the API key and project key to the NeetoPlaydash sharding endpoint, while the reporter posts run records to its API. The prepare hook runs Husky setup, and the inspected process execution is tied to the invoked Playwright workflow.
Decision evidence
public snapshot- package.json points to the reporter bundles and CLI; its prepare hook runs husky install.
- The CLI reads the project key and API key from command-line options, reporter configuration, or named environment variables.
- The sharding flow sends shard and test data with the supplied API and project keys to the configured service, defaulting to connect.neetoplaydash.com.
- Both reporter bundles configure the NeetoPlaydash service endpoint and post run records to its reporter API.
- The CLI launches Playwright with its reporter and writes the service-returned test list to a temporary file for the run.
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.4.1.
See all versions of @bigbinary/neeto-playwright-reporter for other recorded verdicts.
- Review the evidence and your use of @bigbinary/neeto-playwright-reporter@3.4.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.