CodeSampleX

Recordsnpmtype-is1.6.18

Change the conditions
Fixed
OSubuntu glibc Package version1.6.18
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

type-is @1.6.18ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (1)

Project observations
7 / 7
Contract verifications
0 / 2
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-20
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

1.6.18

linux · node@22.23 · moduleSystem=esm · executionContext=node

2 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

View exact conditions View failure cluster
Library Version Health Measured there Projects
media-typer 0.3.0 CANDIDATE Correlated change; unproven combination contract passed 15 project-days
mime-types 2.1.35 CANDIDATE Correlated change; unproven combination contract passed 18 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.

Library2.1.01.6.18
media-typer 1.1.1 0.3.0
mime-types 3.0.2 2.1.35
content-type 2.0.0 —

Moved: 2 · unchanged at every release: 1

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.

Recent failure clusters