tags as prompt inyecttion

[8picota2025]

Have a full recheck, thanks a lot for your efforts

[Spinulosa1111]

Thanks for the report! To investigate this we need a bit more detail:

• Which specific tags are triggering the injection?
• Where does the injection occur (search results, generated design system output, etc.)?
• Steps to reproduce — what exact query/command did you run?
• Expected vs actual output

Please reopen with these details and we'll take a look.

[mrgoonie]

Summary: I rechecked the issue, but there still is not enough evidence to confirm a prompt-injection bug.

Decision: needs-info / needs reproduction

Evidence:

• The issue body only says "Have a full recheck" and does not include the exact tag text, command/query, generated output, or affected install/version.
• The earlier maintainer question asked for the same missing details: triggering tags, where the injection appears, reproduction steps, expected output, and actual output.
• Without a concrete input/output pair, I cannot separate a real prompt-injection handling flaw from a generic security concern.

Next step: please paste the smallest reproducible case:

• exact command or prompt/query used
• exact tag/content that is being treated as prompt injection
• install method and CLI/version if applicable
• expected result
• actual output/error/screenshot

Once those details are here, this can be validated against the parser/search/generation path instead of guessed from the title.

[mrgoonie]

Maintainer note: I rechecked this again during the maintenance pass. There is still no concrete input/output pair to validate, and the latest issue update does not add the missing reproduction details. This remains needs-info / needs reproduction. Please paste the exact tag/content, command or prompt/query, affected install/version, expected result, and actual output/error/screenshot before this can be treated as a confirmed prompt-injection bug.

[clark-cant]

Maintainer follow-up (2026-06-26): This issue has been open for 21 days with maintain:needs-info and decision:needs-repro labels. Three separate maintainer requests for reproduction details have received no response.

Stale closure notice: Without a concrete reproducible case, this will be closed as stale in approximately 5 days (around 2026-07-01).

To keep this open, please provide:

• Exact tag/content that triggers the alleged prompt injection
• Exact command or prompt/query used
• Install method and CLI/version
• Expected result vs actual output/error/screenshot

The security concern is taken seriously, but without a specific input/output pair, we cannot validate it against the parser/search/generation pipeline.

Posted by github-maintain cron at 2026-06-26T11:22:58Z