@kaydash9999/banker-plugins@0.25.1
banker — Claude Code + Codex CLI plugin (QA, audit, docs, architecture, wiki skills). Install via Claude Code marketplace, or `npm i -g @kaydash9999/banker-plugins` then `banker setup`.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe source shows no install-time data collection or unrequested account action. Runtime counting is disclosed, limited to version, platform, and aggregated skill counts, and has opt-out controls; the GitHub star action requires affirmative interactive input.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs a version consistency check.
- The GitHub star action requires an interactive prompt and runs only after an affirmative response.
- The usage check-in payload contains only package version, platform, and aggregated skill counts; the package documents the default-on collection and opt-out methods.
- Agent setup and hook installation run through the explicit banker setup command.
- Runtime usage counting is enabled by default and sends check-ins to the maintainer's endpoint, but this is disclosed and has opt-out controls.
- The CLI can star the publisher's repository using the user's GitHub CLI credentials, but only after the user accepts its prompt.
Source & flagged code
15 flaggedManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
bin/banker.jsView on unpkgPackage source references dynamic require/import behavior.
bin/banker.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to @kaydash9999/banker-plugins@0.25.1.
See all versions of @kaydash9999/banker-plugins for other recorded verdicts.
- Review the evidence and your use of @kaydash9999/banker-plugins@0.25.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.