any-match 2.0.1
Determine if a single match exists with an array of strings/numbers/regexes.
any-match@2.0.1 was published on 2019-04-22. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 6.
All any-match versions · Permanent reference to 2.0.1 · Latest release
Package specifications
| Version | 2.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2019-04-22T19:55:36.855Z |
| Node.js requirement | >= 6 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 3.96 KiB |
| Published file count | 6 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 3 |
| Repository forks | 1 |
Install any-match 2.0.1
npm install any-match@2.0.1 pnpm add any-match@2.0.1 yarn add any-match@2.0.1
Runtime dependencies
- is-regexp ^2.1.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- is-regexp@2.1.0 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 1/10 — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1 |
|---|---|
| SAST | 0/10 — no SAST tool detected |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Code-Review | 0/10 — Found 0/6 approved changesets -- score normalized to 0 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/any-match/2.0.1 — retrieved 2026-10-31T23:47:36.131Z
- https://api.deps.dev/v3/systems/npm/packages/any-match/versions/2.0.1 — retrieved 2026-10-31T23:47:36.679Z
- https://api.deps.dev/v3/systems/npm/packages/any-match/versions/2.0.1:dependencies — retrieved 2026-10-31T23:47:36.698Z
- https://api.deps.dev/v3/projects/github.com%2Fstevenvachon%2Fany-match — retrieved 2026-10-31T23:47:37.061Z