sindresorhus/npm-name

Issues

• Please bump got to 12.1 to fix Vuln

  #47 opened 10 months ago by llbbl
  0

• Package name too similar to existing package node; try renaming your package to '@catpea/noxe

  #48 opened a year ago by catpea
  1

• `got` dependency needs to be updated to patched version

  #46 opened 2 years ago by rob-omb
  0

• TypeError: Cannot destructure property 'statusCode' of 'error.response' as it is undefined.

  #44 opened 3 years ago by VintorezVS
  2

• Update to reflect new registry typosquat restrictions

  #15 opened 4 years ago by ashleygwilliams
  8

• automatically check both organisation and package names

  #39 opened 5 years ago by mesqueeb
  1

• npmName.many error

  #29 opened 5 years ago by ZYSzys
  1

• Support for organization

  #14 opened 5 years ago by rmariuzzo
  5

• Allow overriding the registry URL

  #31 opened 6 years ago by itaisteinherz
  5

• False positive "idb-storage"

  #35 opened 6 years ago by eight04
  1

• Show time of last publish and number of recent downloads if unavailable

  #11 opened 6 years ago by jgallen23
  3

• Flaky results, especially with `pinto`

  #13 opened 6 years ago by haltcase
  3

• Names with '-' wrongly reported as available

  #25 opened 6 years ago by silverwind
  2

• Invalid name reported as available

  #21 opened 7 years ago by astur
  1

• Support for scoped packages

  #17 opened 7 years ago
  2

• Dependency `electron` not found (in `got`) when used in Next project

  #16 opened 7 years ago by lacymorrow
  2

• Add timeout to 'got' request

  #10 opened 7 years ago by yanivefraim
  1

• `got` is unreliable for making requests

  #12 opened 7 years ago by niftylettuce
  1

• Does not support private registries.

  #9 opened 9 years ago by wmfeht
  1

• proxy support

  #1 opened 10 years ago by tardyp
  2

• 404 code break npm-name behavior

  #2 opened 10 years ago by ghoullier
  5