{
  "id": 17241315,
  "title": "No, npm, “estee” is not a typo of “testem”",
  "url": "https://urgent.news/2026/10/30/no-npm-estee-is-not-a-typo-of-testem",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-30T15:01:56.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://smoores.dev/post/no_npm_estee_is_not_a_typo/"
  },
  "original_language": "en",
  "account": "The controversy began when the Storyteller platform's npm command line tool, initially named \"@storyteller-platform/align\", sparked concerns as it was deemed too similar to the existing \"testem\" package. The developer, understandably unhappy with the similarity, coined the nickname \"estee\" as a workaround. However, npm's automated typosquatting system blocked \"estee\" due to its Levenshtein distance of 2 from \"testem\". The developer argues that the current typosquatting rule is ineffective and even potentially harmful, as it could inadvertently block useful package names. They also note that the rule's strictness would have blocked popular npm packages like \"preact\" and \"estree\". The developer feels disappointed by the limitation on 1-, 2-, 3-, and 4-character npm package names, not out of scarcity but due to the rule's impracticality. Despite the issue with \"estee\", the developer believes the platform will continue just fine and plans to try \"estie\" instead.",
  "summary": null,
  "key_points": [
    "Developer coined nickname \"estee\" for npm package",
    "npm blocked \"estee\" due to similarity with \"testem\"",
    "Developer criticizes typosquatting rule as ineffective"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}