chore: add npm keywords for registry search discoverability - #200
Merged
Conversation
@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
Contributor
Author
|
[REVIEW] GO — #200 @ c4fa1b0 — lens: correctness+security+gates, reviewer unresolved-account003 (1 of 1) What I ran:
What I read:
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@hasna/emails(currently 1.3.7 on the registry) publishes with an emptykeywordsarray, 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
descriptionfield andREADME.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 JSONkeywordsinsertion inpackage.json, nothing elsenode scripts/scan-staged-secrets.mjs— exit 0, cleanNeed help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.