Skip to content

chore: add npm keywords for registry search discoverability - #200

Merged
andrei-hasna merged 1 commit into
mainfrom
be4e6956-npm-keywords
Aug 5, 2026
Merged

chore: add npm keywords for registry search discoverability#200
andrei-hasna merged 1 commit into
mainfrom
be4e6956-npm-keywords

Conversation

@andrei-hasna

@andrei-hasna andrei-hasna commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Summary

@hasna/emails (currently 1.3.7 on the registry) publishes with an empty
keywords array, so it does not surface in npm registry search results.
This adds a keyword list to the published root manifest.

Keywords added, derived from the package's own description field and
README.md (verified against the file content, not invented): email,
smtp, ses, resend, cloudflare, sqlite, self-hosted, cli,
mcp, ai, coding-agent.

Metadata-only diff — no version bump, no other files touched, no build
output changed.

Test plan

  • python3 -c "import json; json.load(open('package.json'))" — valid JSON
  • Diff scoped to a single 13-line keywords insertion in package.json, nothing else
  • Staged secrets scan (mandatory pattern set) — 0 matches
  • Repo's own node scripts/scan-staged-secrets.mjs — exit 0, clean
  • Not merged, published, or version-bumped by this PR — left for the release owner

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@hasna/emails published with an empty keywords array, so it does not
surface in npm registry search results. Add keywords derived from the
package's own description and README (email providers, storage, and
interface surfaces) so the package is findable.

Agent: Maecenas
@andrei-hasna

Copy link
Copy Markdown
Contributor Author

[REVIEW] GO — #200 @ c4fa1b0 — lens: correctness+security+gates, reviewer unresolved-account003 (1 of 1)

What I ran:

  • bun install — exit 0. Setup only; not counted as the repository test gate.
  • bun run test — exit 0: 4,289 pass, 156 skip, 0 fail across 288 files (4,445 tests; 20,928 expect calls).
  • The repository declares no typecheck script, so no typecheck gate was invented or run.

What I read:

  • git log --oneline origin/main..HEAD at base 2dbc7ee0f66babe34ee6e45d7a20af69c5de52e5 and head c4fa1b0ecd77155dd6359e9bc056e22c3e846188.
  • git diff origin/main...HEAD --stat.
  • The complete diff for every changed file: package.json only, adding 13 lines of npm keyword metadata.
  • The full surrounding package.json at both the PR head and origin/main.

Blocking P0/P1 findings: none. The change is package-discovery metadata only and introduces no runtime, authorization, credential, data-integrity, mutation, migration, or rollback path.

Non-blocking follow-ups: none.

@andrei-hasna
andrei-hasna merged commit fda89b5 into main Aug 5, 2026
4 checks passed
@andrei-hasna
andrei-hasna deleted the be4e6956-npm-keywords branch August 5, 2026 01:10
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.

1 participant