Recordsnpmcontent-disposition2.0.1
Change the conditions
Current conditions
content-disposition @2.0.1debian glibc · x64 · node 22 · npm · node
package-level total, not an API
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-10-21
Evidence you can open
Dependency Health
A resolution read this release's tree and found no dependencies. That is a measurement, not a missing one.
Recent failure clusters
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 2.0.1 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:ef96efaca8dd…AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · undefined !== 123 · at <url> …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-21 · Last seen: 2026-10-21