Skip to content
JS
Package

package-name-conflict

Check if NPM package names conflict

v1.0.3, 7 Apr 2021MITCommonJSTypes: NoneTypeScript tooling
$ npm install package-name-conflict

Key numbers

As of 25 Sept 2026
Weekly downloads
5.4k
-59% over 12 months
Gzip bundle size
-
No Bundlephobia data
Dependencies
0
Direct, from package.json
Last release
5 years ago
v1.0.3
GitHub stars
1
0 forks
Open issues / PRs
0 / 0
Contributors
-
Commits, last 52 weeks
0

Downloads

Last week 2026-09-15 to 2026-09-21
010k20k30kSept 2025Mar 2026Sept 2026High 20.3k (21 Oct 2025)Low 1.8k (23 Dec 2025)
Weekly npm downloads, one point per week, weeks starting 23 Sept 2025 to 15 Sept 2026. The y axis starts at zero.

5,368 downloads last week, 23,008 in the last month. The 12-month change of -59% compares the average of the last 4 weeks with the first 4 weeks of the series.

Releases, last 12 months
-
Latest version
1.0.3, 7 Apr 20215 years ago
First published
-
Last push to GitHub
7 Apr 20211,997 days before the snapshot
Repository archived
No
Open issues
0
Open pull requests
0
Commits, last 52 weeks
0
Dependents on npm
1

Major versions

-

Recent releases

-

Module format
CommonJSFrom package.json type, main and exports fields
TypeScript types
None
Node.js engine range
Not declared
Runtimes
-
Unpacked size (npm)
5.4 kB
Dependencies (0)
None
npm install package-name-conflict
  • jsDelivrhttps://cdn.jsdelivr.net/npm/package-name-conflict@1.0.3/
  • unpkghttps://unpkg.com/package-name-conflict@1.0.3/
  • esm.shhttps://esm.sh/package-name-conflict@1.0.3
Sources: npm registry, npm downloads API, GitHub API. Data fetched 25 Sept 2026.

Indexability: Not indexed (discovery only): downloads_week 5368 < 10000.