ai-test-fixer@1.0.6
AI-powered test-driven code generation and automated test repair CLI and toolkit
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe default configuration selects Gemini and its provider silently falls back to a package-embedded key, while the README describes the default as a zero-configuration option without disclosing that project context is sent to Google. This is an undisclosed runtime data flow tied to the package's AI feature, so it warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- The default configuration selects Gemini, while the README describes running the default command as zero-configuration and requiring no API key.
- Gemini falls back to an API key embedded in the package when no Gemini key is configured.
- Gemini sends the generated user prompt to Google's generateContent endpoint using that key.
- The CLI defaults to the `fix` command, which can trigger project-context generation.
- The package has no install lifecycle scripts.
- The network request occurs as part of the AI repair feature, rather than on import.
- Gemini requests go to Google's API endpoint, and a user can choose a local Ollama provider.
Source & flagged code
6 flaggedPackage contains a high-severity secret pattern.
src/providers/gemini.jsView on unpkg · L18Gemini falls back to an API key embedded in the package when no Gemini key is configured.
src/providers/gemini.jsView on unpkg · L18Findings
Affected versions and remediation
This report applies to ai-test-fixer@1.0.6.
See all versions of ai-test-fixer for other recorded verdicts.
- Review the evidence and your use of ai-test-fixer@1.0.6 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.