npm · npm:wildcard

wildcard active

Wildcard matching tools

The latest stable version of wildcard is 2.0.1, published on 2023-04-24. Verified by Vigia on 2026-11-12.

Latest stable version	2.0.1
Published	2023-04-24 14:00:51 UTC
Install	`npm install wildcard@latest`
Requires (engines)	none declared
Peer dependencies	—
Dist-tags	`latest: 2.0.1`
License	MIT
Advisories on latest version	none known
Last verified	2026-11-12 12:54:50 UTC
Sources	api.deps.dev, registry.npmjs.org, registry.npmjs.org

Ask your AI assistant to check this

AI models are trained up to a date, so they can be wrong about versions, deprecations and vulnerabilities. Paste this into Claude, ChatGPT, Perplexity or Cursor and it will answer with the verified data on this page:

Before answering about the npm package "wildcard", check Vigia (verified, dated facts): https://vigia.coredls.cloud/v1/packages/npm/wildcard . For my whole project use https://vigia.coredls.cloud/context

Check my whole package.json

Using an AI coding agent every day? Connect Vigia once and it checks this by itself.

Maintenance

Activity	dormant
Last stable release	2023-04-24 14:00:51 UTC · 1298 days ago
Stable releases in the last 12 months	0
Published versions	11

Heuristic based only on release dates; it does not measure issue or security response times.

Version history

Version	Published
`2.0.1`	2023-04-24 14:00:51 UTC
`2.0.0`	2019-06-24 09:50:38 UTC
`1.1.2`	2015-04-21 23:36:50 UTC
`1.1.1`	2015-04-20 00:05:42 UTC
`1.1.0`	2014-10-02 07:00:19 UTC
`1.0.0`	2014-09-07 23:10:25 UTC
`0.1.5`	2014-06-08 09:11:05 UTC
`0.1.4`	2013-05-05 10:48:30 UTC
`0.1.3`	2012-10-29 22:40:53 UTC
`0.1.2`	2012-07-24 00:48:58 UTC
`0.0.1`	2012-03-13 10:02:05 UTC

Showing the 11 most recent of 11 versions. JSON

Version compatibility

Newest stable version that declares support for each runtime version (from the requirements published with each version).

Runtime	Newest compatible version
`node 16`	`2.0.1`
`node 18`	`2.0.1`
`node 20`	`2.0.1`
`node 22`	`2.0.1`
`node 24`	`2.0.1`

Give your AI agent these facts

Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.

claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp

Add to Cursor Add to VS Code ★ Star on GitHub

Any other MCP client

{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }

Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests

Frequently asked questions

What is the latest version of wildcard?

The latest stable version of wildcard is 2.0.1, published on 2023-04-24. Verified by Vigia on 2026-11-12.

How do I install the latest version of wildcard?

Run npm install wildcard@latest. The latest stable version is 2.0.1 (verified 2026-11-12).

Is wildcard deprecated?

No. wildcard is not marked as deprecated in the registry.

Which Node.js version does wildcard require?

wildcard 2.0.1 does not declare a Node.js version requirement.

Does wildcard 2.0.1 have known vulnerabilities?

No known advisories affect wildcard 2.0.1 according to the data Vigia checks.

Is wildcard still maintained?

wildcard published 0 stable releases in the last 12 months; the most recent was 1298 days ago. Activity: dormant.

Observed changes

No changes observed yet since Vigia started tracking this package.

Related packages

Badges for your README

Show the latest version, maintenance status and deprecation status of this package. Copy the Markdown:

[![version](https://vigia.coredls.cloud/badge/npm/wildcard/version.svg)](https://vigia.coredls.cloud/npm/wildcard)
[![maintained](https://vigia.coredls.cloud/badge/npm/wildcard/maintained.svg)](https://vigia.coredls.cloud/npm/wildcard)
[![status](https://vigia.coredls.cloud/badge/npm/wildcard/status.svg)](https://vigia.coredls.cloud/npm/wildcard)

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/wildcard
GET https://vigia.coredls.cloud/v1/packages/npm/wildcard/versions/{version}