Where does the version data come from?

From the public npm registry, read live via its keyless API. Each figure Zeplik returns, the latest version, publish date, license, and downloads, is the registry's own current record.

Why not just ask a chatbot for the latest version?

Because a language model's memory of npm versions froze at training time and is almost always out of date, so any version it names from memory is likely wrong. This reads the live registry instead.

Do scoped packages work?

Yes. Names like @tanstack/react-query or @types/node resolve the same way as unscoped ones, and the answer includes the same live version and metadata.

Will it warn me if a version is deprecated?

Yes. If the registry marks the latest version deprecated, Zeplik surfaces that in the answer so you do not install something the maintainers have pulled back.

Does an npm lookup cost credits?

The lookup itself is free. You pay only the normal model-token cost of the answer Zeplik writes around it, shown before you send, exactly like any other message.

Look up the real latest npm package version

Ask about any npm package and Zeplik reads its real record straight from the public npm registry, then answers with the actual latest version, when it was published, the license, the dependency count, and weekly downloads. A language model's memory of package versions froze at training time and is almost always stale, so a version it recalls is usually wrong. This reads the live registry and, when a package does not exist, says so instead of inventing a version.

Look up a Python package

The lookup is free; you pay only the normal cost of the answer, shown before you send.

How it works

Name the package
Ask in plain language, like 'what is the latest version of react?' or 'show me the current version and license for next'. Scoped names like @scope/name work too.
Zeplik reads the npm registry
It queries the public npm registry for that exact package, not the model's memory, and treats the record as source data with its version, dates, license, and download counts.
Read the live record
The answer states the latest version with its publish date, the license, the dependency count, the other dist-tags, and weekly downloads, all current as of the moment you asked.

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 details.

Prompt: What is the latest version of react, and when was it published?

Zeplik reads the registry and returns the current latest version with its exact publish date, so you are not relying on a version the model half-remembers.

Open this in Zeplik

Prompt: Show me the current version, license, and weekly downloads for next

It returns the live version, the SPDX license, and the real weekly download count from the registry, not an estimate.

Open this in Zeplik

Prompt: Is @tanstack/react-query up to date, and what is its latest release?

Scoped packages resolve fine; it reports the latest published version and flags the release if the registry marks it deprecated.

Open this in Zeplik

What it can and cannot do

The lookup is precise about what it can verify and honest about its edges. Here is the plain posture.

Does itThe real latest version

Zeplik reads the registry's current latest dist-tag, so the version is the one published right now, not a stale guess.

Does itPublish date and license

Every lookup carries the exact publish timestamp and the declared license, straight from the registry record.

Does itDownloads and dependency count

It reports real weekly downloads and how many runtime dependencies the latest version declares.

Does itHonest when a package is missing

If no such package exists on the registry, Zeplik says so rather than inventing a version to fill the answer.

Does notJudging whether a package is safe to install

It reports registry facts, not a security audit. For known vulnerabilities, pair it with a dedicated advisory lookup rather than trusting a vibe.

Does notPrivate or unpublished packages

It reads the public registry only, so private-registry or unpublished packages will simply come back as not found.

Grounded, and honest by default

It cites the version and its date. Every answer states the latest version with the exact publish timestamp from the registry, so nothing is approximated.
It will not invent a version. A language model's package knowledge is frozen and stale, so when a package is missing Zeplik says so rather than naming a plausible version.
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

Where does the version data come from?: From the public npm registry, read live via its keyless API. Each figure Zeplik returns, the latest version, publish date, license, and downloads, is the registry's own current record.
Why not just ask a chatbot for the latest version?: Because a language model's memory of npm versions froze at training time and is almost always out of date, so any version it names from memory is likely wrong. This reads the live registry instead.
Do scoped packages work?: Yes. Names like @tanstack/react-query or @types/node resolve the same way as unscoped ones, and the answer includes the same live version and metadata.
Will it warn me if a version is deprecated?: Yes. If the registry marks the latest version deprecated, Zeplik surfaces that in the answer so you do not install something the maintainers have pulled back.
Does an npm lookup cost credits?: The lookup itself is free. You pay only the normal model-token cost of the answer Zeplik writes around it, shown before you send, exactly like any other message.

Related skills

More on Zeplik

Install the right version

Look up the real latest npm package version, its publish date, license, and downloads, live from the registry, with an honest answer when a package does not exist. Free to start.

Look up an npm package Browse all tools