Recordsnpmtough-cookie6.0.2
Change the conditions
Current conditions
tough-cookie @6.0.2windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
6.0.2
linux · node@22.23 · moduleSystem=esm · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:529aac3b1da710068c9dcfe93d0864269e86bebfbe110ca5beeed398860460e7
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| tldts | 7.4.11 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 6.0.2 | 6.0.0 | 5.1.2 | 4.1.4 |
|---|---|---|---|---|
| tldts | 7.4.11 | 7.0.19 | 6.1.86 | — |
| psl | — | — | — | 1.15.0 |
| punycode | — | — | — | 2.3.1 |
| universalify | — | — | — | 0.2.0 |
| url-parse | — | — | — | 1.5.10 |
Moved: 1 · unchanged at every release: 4
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.