landmine

landmine_check takes a code snippet and landmine_lookup takes package versions, so the input type is the main differentiator and the descriptions make it clear. There is still conceptual overlap — both answer 'what open issues affect these exact versions?' — so an agent with code in hand could plausibly pick either, but the boundary is workable.

Both tools follow the identical prefix_verb pattern (landmine_check, landmine_lookup), giving a clear, predictable namespace. No mixing of conventions.

Two tools is thin for the surface — there is exactly one operation per input type (code vs. dependency list). It is defensible for a narrow purpose, but there is no room for supporting operations like listing affected versions or fetching a single issue.

The two entry points cover the two realistic workflows: auditing existing code and vetting a dependency before adding or upgrading it, and results include evidence and workarounds. Minor gaps remain — no way to retrieve a specific issue or enumerate known-affected versions — but core workflows are covered.