@bigbinary/neeto-playwright-reporter@4.0.5
The custom playwright reporter for neeto-playwright-dashboard.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe execution signal comes from fixed Git metadata queries in the reporter, while its network requests send report data to the configured NeetoPlaydash API. The prepare hook only installs Husky, and the inspected sources show no secret harvesting or unrelated recipient.
Decision evidence
public snapshot- The manifest points to the reporter and CLI entrypoints; its prepare hook runs Husky installation.
- The reporter uses fixed Git commands to collect commit, author, and branch metadata for a run.
- The reporter uses the NeetoPlaydash API, with its default host and API credentials taken from reporter configuration or environment settings.
- The CLI passes Playwright arguments to the Playwright process and inherits its environment and standard streams.
- The required dependency excerpts show standard Axios cancellation handling, utility-library imports, and a Honeybadger client whose default API key is unset.
- The dependency root exports the Axios client together with its cancellation and configuration helpers.
- Static signals flag shell execution and networking, but the inspected shell commands are fixed Git metadata queries and the network calls serve the reporter’s dashboard workflow.
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.5.
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.5 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.