Skip to content

docs: cross-link the ssrf-guard-js sibling from README + docs index#16

Merged
jlc488 merged 1 commit into
mainfrom
docs/js-sibling-crosslink
Jul 12, 2026
Merged

docs: cross-link the ssrf-guard-js sibling from README + docs index#16
jlc488 merged 1 commit into
mainfrom
docs/js-sibling-crosslink

Conversation

@jlc488

@jlc488 jlc488 commented Jul 12, 2026

Copy link
Copy Markdown
Collaborator

What

The JS/TS port (@devslab/ssrf-guard-js) has been on public npm since 0.3.0 and the org profile lists both projects — but nothing in this repo pointed readers at it.

  • README.md / README.ko.md: new "TypeScript / JavaScript sibling" section (before Requirements) mapping the surfaces: validateUrlUrlPolicy, safeFetch ↔ this project's DNS-time guards, guardedFetch for Workers/browsers, guardToolInputJson-llm/-springai/-langchain4j.
  • docs/index.md / index.ko.md: sibling row in "Where it lives".

Docs-only — no code, no version bump.

Context

Part of the guardedFetch rollout on the JS side (ssrf-guard-js#10).

The JS/TS port (@devslab/ssrf-guard-js) has been on public npm since
0.3.0 and the org profile links both projects, but nothing in this
repo pointed readers at it — a Java reader asking 'is there a JS
version?' had no answer. New section in both READMEs (before
Requirements) and a row in the docs-site index's 'Where it lives'
list, mapping the surfaces: validateUrl <-> UrlPolicy, safeFetch <->
the DNS-time guards, guardedFetch for Workers/browsers, and
guardToolInputJson <-> -llm/-springai/-langchain4j.
@jlc488
jlc488 merged commit 882c1de into main Jul 12, 2026
1 check 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.

1 participant