foresee

foresee predicts the package names an AI is likely to invent for your project and checks whether anyone has already registered them as traps.

vulkro-live foresee            # current directory
vulkro-live foresee ./api --limit 40

$ vulkro-live foresee . --limit 20

foresee: checked 20 predicted name(s) your AI might invent for this npm project (./package.json).

No planted trap found: none of the predicted names is a registered squat yet.

Wrote 4 name(s) to ./.vulkro-foresee.json (point your agent at it: never install any of these).

It reads your dependency manifest, builds likely-but-absent names from it (no AI model involved), and checks each one with the same registry lookups as verify. A predicted name that is already registered, recently and with almost no downloads, is reported as a TRAP.

Names that do not exist yet go into .vulkro-foresee.json. Commit it and tell your agent never to install anything on the list:

{
  "do_not_install": ["axios-util", "axios-helper", "axios-cli", "axios-js"],
  "ecosystem": "npm",
  "note": "Package names your AI might hallucinate for this project. Do not install any of these unless you deliberately and independently confirmed it.",
  "planted_traps": []
}

Flags

Flag	Effect
`[DIR]`	Project directory (default: current)
`--limit <n>`	How many predicted names to check (default 80). Each is one registry lookup
`--no-write`	Do not write `.vulkro-foresee.json`
`--no-cache`	Skip the local cache
`--format <FORMAT>`	`text` (default), `json` or `sarif`

Exit codes: 0 no trap found, 1 a predicted name is already a trap, 2 error.

The vulkro scanner has an offline counterpart, vulkro slopcheck.

Flags​

Flags