Skip to content

fix: publish under the @logfox scope - #2

Merged
mhweiner merged 1 commit into
mainfrom
feat/scope-package-under-logfox
Sep 2, 2026
Merged

fix: publish under the @logfox scope#2
mhweiner merged 1 commit into
mainfrom
feat/scope-package-under-logfox

Conversation

@logfox-agent

Copy link
Copy Markdown
Collaborator

Summary

npm refuses the unscoped name busker:

403 Forbidden - PUT https://registry.npmjs.org/busker
Package name too similar to existing packages buffer,bser,user

npm's typosquat check is edit-distance based against popular packages, not an exact-name check — busker is two edits from each of those. Short unscoped names are unlikely to clear it, so the package publishes as @logfox/busker.

Only the npm specifier changes. The project, the repo, the docs site, busker.logfox.ai, and the busk() API all keep the busker name.

  • package.json name → @logfox/busker (publishConfig.access: public was already set, which scoped packages need)
  • Install and import lines updated in the README and in the getting-started, api-reference, and styling docs

Test plan

  • npm run validate green
  • npm pack --dry-run produces logfox-busker-0.1.0.tgz with the same 14 files
  • No remaining references to the unscoped specifier

npm rejects the unscoped name as too similar to buffer, bser, and user.
Its typosquat check is edit-distance based against popular packages, so
any short unscoped name is unlikely to get through.

Only the package specifier changes; the project, the repo, and the busk()
API keep the busker name.
@mhweiner
mhweiner merged commit 99f9d35 into main Sep 2, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants