Repository navigation
Improve Node SDK branding and discoverability - #83
Merged
Merged
Conversation
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.
The repository opened with a narrow tripwire headline and no WebDecoy branding, while the SDK also supports AI agent verification and crawler policies. Add a branded banner, CI/npm/type/license badges, a searchable SDK heading and a framework chooser, keeping the existing technical reference and keyless install path.
Validation: inspected the rendered banner; root README local links and heading anchors pass; JSON parses;
git diff --checkpasses; npm pack dry run includes README at unchanged version 0.22.3. Runtime code is unchanged. CI badge returned HTTP 200; direct docs/Shields probes returned 403, so those external endpoints were not independently validated by that probe.GitHub About description, docs homepage and 20 relevant topics are updated live. The PNG is also uploaded as the repository social preview; the saved image was visually verified and GraphQL confirms
usesCustomOpenGraphImage: true. Both Node 20 and Node 22 CI jobs passed, including build, lint, tests and edge checks.