Keywords array for discoverability

An empty or missing keywords array in package.json removes the package from npm's keyword-indexed search results, so developers looking for an SDK in your domain will never surface it through the registry's discovery surface. Generic keywords like javascript or node are functionally equivalent to no keywords — they collide with hundreds of thousands of unrelated packages. This failure maps directly to the findability taxon and directly suppresses organic installs, GitHub traffic, and ecosystem integrations that depend on npm search.

Add a keywords array to package.json with at least five specific terms that describe the package's domain, protocol, and ecosystem. Avoid generic words like javascript, library, or utility; instead name the service, the transport, the framework, and the problem category so that npm's search ranks the package for relevant queries.

{
  "keywords": [
    "api-client",
    "rest-api",
    "typescript",
    "sdk",
    "your-service-name"
  ]
}