@roopesh.yadava/qa-pack@1.9.1
AI-powered QA agent skills for Claude Code — manual testing, BDD automation, accessibility, UI/Figma diff, bug reporting
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe postinstall hook expands Claude’s browser-tool permissions without an affirmative consent check, creating a concrete agent capability risk. The permission is scoped to the package’s Playwright QA integration, so the evidence supports a warning rather than a publish block.
Decision evidence
public snapshot- The manifest runs bin/postinstall.js during npm postinstall.
- The hook targets the consumer project’s local Claude settings and says it forces the rule on every install or update, including for hand-edited settings.
- The hook adds the Playwright MCP permission and writes the settings file without an affirmative consent check.
- The permission covers the Playwright MCP namespace; the package also supplies a Playwright MCP server for Chromium.
- The Playwright permission is tied to a browser tool supplied by the package for QA work; inspected source did not establish credential export or remote payload execution.
Source & flagged code
14 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
Findings
Affected versions and remediation
This report applies to @roopesh.yadava/qa-pack@1.9.1.
See all versions of @roopesh.yadava/qa-pack for other recorded verdicts.
- Review the evidence and your use of @roopesh.yadava/qa-pack@1.9.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.