tough-cookie
6.1.0 · 6 Nov 2026BSD-3-Clause202.3M / weekRepositorynpmAtom feed
Where each line stands
Plan an upgradeLatest releases
All 51 releases- 6.x · latest line
6.1.0
6 Nov 2026Summary· from the note as AI read it
Read before upgrading: 8 changes to make.
Notable changes
Securecookies are rejected when set from an insecure origin (#656, #663)CookieJarnow refuses to store aSecurecookie set from a URL that isn't potentially trustworthy, such as plainhttp://example.com, per RFC 6265bis §5.7 step 13.https:andwss:URLs are still accepted, and so arelocalhostand loopback addresses whileallowSecureOnLocalis enabled (the default).setCookie()now rejects withCookie is Secure but this is not a secure connection, or drops the cookie silently whenignoreError: trueis passed.This changes behavior that existing v6 code may rely on. To keep storing
Securecookies no matter which origin set them, opt out with:new CookieJar(store, { enforceSecureOriginOnStorage: false })The opt-out applies only to storage. On retrieval,
Securecookies are still returned only for secure origins, the same as in v6.0.x. The setting survivesserialize()/deserialize()andclone().Other behavior changes
__Host-cookies now need an explicitPath=/attribute. Having the default path come out as/is no longer enough (#608).Cookie.validate()now returnsfalsefor names that aren't valid HTTP tokens, such as empty names, names with separators or control characters, and non-ASCII names. Parsing and storage are unchanged (#650).An explicit
SameSite=Noneis now kept when serializing withCookie.toString()andgetSetCookieStrings(); it used to be dropped (#639).An IPv4 address in the
Domainattribute is now accepted instead of being treated as a public suffix (#630).
Additions
6.0.2
7 Jul 2026Review Section 5.1.3. Domain Matching
Avoid decoding URL authority part
Dependency bumps in too many PRs to bother enumerating
6.0.1
12 Mar 2026Review Section 5.1.1. Dates
Adopt npm trusted publishing (OIDC)
Dependency tracking
Know when your own dependencies move
This page watches tough-cookie. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Reading releases, release notes and advisories…
Registry facts last checked 19 Nov 2026. Releases and advisories last read 19 Nov 2026.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.