A finance chatbot relies on a community prompt pack with no active maintainer. What supply risk should the assessment raise?
Select an answer to reveal the explanation.
Short Explanation
An orphaned prompt pack has nobody watching the store—bugs and tricks linger. Own or replace it.
Full Explanation
A finance chatbot that relies on a community prompt pack with no active maintainer presents abandoned community prompt-pack risk. Unmaintained packs leave municipal finance bots without security fixes, integrity updates, or responses to newly discovered prompt-injection patterns. Assessments treat abandoned prompt supply as risk requiring internal ownership, a vetted commercial or curated replacement, or a freeze-and-fork under city change control. Vendor cadence, model pinning, and log retention do not restore prompt-pack maintenance.
Vendor-managed update cadence for licensed finance chatbot modules fails by concept: licensed modules imply active vendor upkeep, not an abandoned community pack. Pinned model version drift in municipal budget reporting workflows is model governance, not supply stewardship for an orphaned prompt pack. Archived transaction log retention for municipal audit compliance reviews is an audit control, not a fix for an unmaintained prompt pack. Distractors confuse adjacent municipal controls with abandoned prompt-pack risk.
Exam caveat: “community popular” is not the same as maintained—check recent commits, issue response, and security advisories; archival repos can still be widely downloaded. Operational check: replace or internally fork the abandoned pack into a city-owned prompt repository with named maintainers, pin the finance chatbot to that revision, monitor for upstream advisories on related patterns, and schedule periodic prompt-security review before budget-season peaks.