Package version checker
Ask for the latest version of any package and Zeplik reads the actual registry, then answers from it. Not the version that was newest when the model was trained, and never an invented number: it queries npm, PyPI, crates.io, RubyGems, or Go modules live, so the answer is right today. Tell it the version you are on and it will say plainly whether you are behind, and by how much.
The lookup is free; you pay only the normal cost of the answer, shown before you send.
How it works
Name the package
Ask about a dependency in plain language, like 'what is the latest version of express?'. Naming the registry (npm, PyPI, crates.io) removes any ambiguity when a name exists in more than one place. You do not have to open the tool explicitly; asking about a package's version is enough for Zeplik to run the lookup.
Zeplik reads the live registry
It queries the package's real registry entry, not the model's training memory, and treats the result as source material. The registry response is handled as untrusted content, so nothing in it can steer the answer off course.
Get the current version and act
The answer states the current published version, and if you named the version you are on, how far behind you are. Ask it to read the changelog, plan the upgrade, or check the next package, all in the same conversation.
Worked examples
Real prompts you can open in the composer with the text ready to review. Nothing sends on its own. Swap in your own package.
Prompt: What is the latest version of react on npm?
Zeplik reads the npm registry and returns the current published version, so the answer is right today, not whatever was newest when the model was trained.
Open this in ZeplikPrompt: Check the current published versions of fastapi and pydantic on PyPI
Ask about several packages at once and each is looked up live, so you can line up a set of Python dependencies in one message.
Open this in ZeplikPrompt: Is my next 13.4.0 out of date? What is the newest release?
Name the version you are on and Zeplik compares it against the live latest, telling you plainly whether you are behind and by how far.
Open this in ZeplikWhat it can and cannot do
The checker is exact about published versions and honest about its edges. Here is the plain posture.
Name a package and Zeplik reads its registry entry for the current published version, updated to the minute rather than to the training cutoff.
The major open-source registries are covered, so a JavaScript, Python, Rust, Ruby, or Go dependency all check the same way.
Tell it the version you are running and it compares against the live latest, so you know whether an upgrade is waiting.
If the name is misspelled or the package does not exist on that registry, Zeplik says so rather than inventing a version number.
It reads public registries anonymously. A package on a private or company-internal registry is out of reach; paste its metadata in instead.
It tells you what the latest version is, not whether it is safe to adopt. For breaking-change and migration help, ask Zeplik to read the changelog or plan the upgrade with you.
Grounded, and honest by default
- It reads the real registry. The version comes from the package's live registry entry, so it is current to the minute rather than to the model's training cutoff.
- It will not invent a version. When a package cannot be found, Zeplik says so rather than guessing a number that looks right.
- Registry data cannot hijack the answer. The registry response is treated as untrusted content: Zeplik reads and reports it but never obeys instructions embedded inside it.
Frequently asked questions
- Why not just ask a chatbot for the latest version?
- Because a language model only knows what existed when it was trained, and package versions move constantly. Asked cold, it will often give you a version that was current months ago, or confidently invent one. This tool reads the live registry, so the number is right today.
- Which registries does it support?
- It covers the major open-source registries, including npm, PyPI, crates.io, RubyGems, and Go modules. Name the package and, when it helps, the registry, and Zeplik returns the current published version from that source.
- Does the lookup cost credits?
- The lookup itself is free. Reading the registry draws nothing from your balance; you only pay the normal model-token cost of the answer Zeplik writes around it, exactly like any other message, and the cost is shown before you send.
- Can it tell me if my version is out of date?
- Yes. Tell it the version you are running and it compares against the live latest, then tells you plainly whether you are behind and by how much. From there you can ask it to read the changelog or help plan the upgrade.
- Can it read a private or internal registry?
- No. It reads public registries anonymously, with no credentials, so a package hosted on a private or company-internal registry cannot be reached. Paste the package metadata into the chat and Zeplik will work from that instead.
- Which AI model does the lookup?
- The registry read is a built-in capability that works the same regardless of model. The answer around it is written by whichever of Zeplik's frontier chat models you pick, and you can switch models at any time, including mid-conversation.
Related skills
Go deeper on managing your dependencies with these ready-to-run Zeplik skills.
More on Zeplik
Stop guessing the version
Read the latest published version straight from the registry, and know when you are behind. Free to start.