is-potential-custom-element-name
Check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard.
npm says
124,412,255
per week
Every tarball fetch: mirrors, scanners, CI and people.
real installs
medium confidence≈ 124M
per week
Mirror spikes and crawlers removed. CI and dependency installs still count, so this is not a head count.
noise under 1% of npm's count, so nearly all of it counts. noise real installs
Why this estimate
With JavaScript on, this lists what the filter found for this package.
Snapshot from the daily build of Nov 10, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people use is-potential-custom-element-name?
npm counted 124,412,255 downloads of is-potential-custom-element-name in the last 7 days. Nobody can count people exactly, npm included: it does not record who downloaded what. After removing mirror spikes and crawlers, about 124M look like real installs. At this scale most of them come from CI, builds and other packages that depend on is-potential-custom-element-name, so the number of people behind them is far smaller.
Is is-potential-custom-element-name still maintained?
Probably not actively: there has been no release in over a year, though that can also mean it is simply finished. The latest version, 1.0.1, came out on Apr 7, 2021. There were no stable releases in the last 12 months. It was first published on Jun 21, 2016. npm lists 1 maintainer.
Is is-potential-custom-element-name still used?
Downloads with publish spikes removed are up 72% over 3 months and up 328% over 11 months. For scale, the median of the 384 packages we track, which lean towards today's most downloaded, is up 164% over 11 months, so this one is ahead of that. Last week, 100% of downloads above the crawler floor were on major version 1, the latest one; the most used single version was 1.0.1, with 100%. Weekdays get 1.6× the downloads of weekends, which fits people at work, though CI follows the same rhythm.
Monthly downloads of is-potential-custom-element-name
The busiest month was Oct 2026, with about 15,767,039 downloads a day once publish spikes are removed; the quietest was Dec 2025 (the holiday season), with about 3,464,723.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 409,943,016 | 0 | 410M | up 25% |
| Sep 2026 | 341,348,555 | 0 | 341M | up 24% |
| Aug 2026 | 317,272,379 | 0 | 317M | up 10% |
| Jul 2026 | 289,492,674 | 0 | 289M | up 11% |
| Jun 2026 | 251,781,918 | 0 | 252M | up 12% |
| May 2026 | 232,983,388 | 0 | 233M | up 8% |
| Apr 2026 | 209,220,273 | 0 | 209M | up 6% |
| Mar 2026 | 204,487,811 | 0 | 204M | up 25% |
| Feb 2026 | 148,310,852 | 0 | 148M | up 31% |
| Jan 2026 | 124,964,624 | 0 | 125M | up 16% |
| Dec 2025 | 107,406,403 | 0 | 107M | — |
Whole months through Oct 31, 2026. Publish spikes are found day by day and summed per month. Real installs apply this week's crawler share to each month's downloads (the upper end also keeps the removed spikes), so they follow npm's curve rather than measure it. The change compares spike-free downloads per day.
How the estimate works
- Cut the spike every new version gets from mirrors in its first days.
- Subtract the flat floor robots download from every version each week.
- Show what is left as a range, with a confidence level. It still includes CI and dependency installs, so it is not a count of people.