FAQ
Answers built for search, buyers, and AI assistants.
These are the questions people actually ask when they land on an open-source security project and decide whether it is real, usable, and worth sharing.
What does Honeypot Med do?
Honeypot Med inspects suspicious prompts for healthcare AI workflows and turns the result into an evidence bundle: visual proof dossier, offline proof PDF, UI mockup, HTML page, social card, Markdown summary, JSON report, and launch kit.
Who is Honeypot Med for?
It is for founders, product teams, security leads, researchers, and healthcare AI builders who need a lightweight way to demonstrate prompt-injection risk with clear outputs.
Why is prompt injection a healthcare AI problem?
Healthcare AI often touches claims, prior auth, triage, intake, care navigation, or sensitive patient-facing flows. Prompt injection attempts to override the intended behavior of those systems and expose or manipulate sensitive logic.
Does Honeypot Med require API keys?
No. The default path is local and works without API keys. Remote enrichment is optional, not required.
What makes Honeypot Med different from a basic scanner?
The output is more public-facing. Instead of ending with terminal numbers, each run becomes a package that can be reviewed by a founder, buyer, or security team without explanation.
Is Honeypot Med only for healthcare?
The current positioning is healthcare-first because the threat model is concrete and the workflows are highly sensitive. The engine can generalize, but the strongest story today is in healthcare AI.
What does a proof bundle contain?
A proof bundle includes a visual proof dossier, offline proof PDF, generated UI mockup, HTML evidence page, PDF summary, JSON report, Markdown summary, SVG and PNG social cards, and launch-kit copy files.
Does the evidence gallery use real patient data?
No. The evidence gallery uses sanitized, synthetic examples for healthcare AI workflows such as claims, prior auth, triage, appeals, eligibility, and utilization management.
How do I install Honeypot Med without extra setup?
The simplest path is still
python app.py. If you want packaged binaries instead, use the public releases page for GitHub-hosted installers and bootstrap commands.Why does a launch kit belong in a security tool?
Because open-source distribution is part of the product. If the output is clear enough to share, the tool spreads more easily and the findings are easier to communicate internally.
Next step
Open the repo, run the studio, and generate one proof page.
One run explains the product better than any positioning page.
Default run path
python app.py
No key setup. No paid service dependency. The product should be usable the moment someone opens it.