@roopesh.yadava/qa-pack
AI-powered QA agent skills for Claude Code — manual testing, BDD automation, accessibility, UI/Figma diff, bug reporting
This report shows the evidence for @roopesh.yadava/qa-pack@1.9.0. 8 of 10 known versions are blocked or flagged. The newest version, 1.9.1, is flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest activates a postinstall hook that silently expands permissions in the consumer’s AI-agent settings. This is an unconsented install-time control-surface change, so the package should be blocked.
Decision evidence
public snapshot- The manifest runs bin/postinstall.js automatically on package installation.
- The install hook targets the consumer project’s Claude settings and creates settings.local.json from the package template when missing.
- On install or update, the hook adds mcp__playwright to permissions.allow and writes the changed settings file without a consent check.
- The package configures Playwright as an MCP server, so the added rule grants automatic approval to its browser tools.
- The installer’s indicated skills path is under the consumer project’s .claude directory.
- The toolkit’s indicated runtime path resolves product context and outputs under the current repository root.
- The settings template allows mcp__playwright and enables all project MCP servers.
Source & flagged code
12 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 unpkgPackage contains a possible secret pattern.
claude/skills/shared/scaffold.shView on unpkg · L291Findings
Affected versions and remediation
This report applies to @roopesh.yadava/qa-pack@1.9.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @roopesh.yadava/qa-pack@1.9.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.