CodeSampleX

Recordsnpm@semantic-release/commit-analyzer13.0.1

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

Current conditions

@semantic-release/commit-analyzer @13.0.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 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 failed

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 8

First observed break

13.0.1

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
conventional-changelog-angular 8.3.1 PASS All observations passed contract passed 3 project-days
conventional-changelog-writer 8.4.0 PASS All observations passed contract passed 3 project-days
conventional-commits-filter 5.0.0 PASS All observations passed contract passed 3 project-days
conventional-commits-parser 6.4.0 PASS All observations passed contract passed 3 project-days
debug 4.4.3 PASS All observations passed contract passed 3 project-days
import-from-esm 2.0.0 PASS All observations passed contract passed 3 project-days
lodash-es 4.18.1 PASS All observations passed contract passed 3 project-days
micromatch 4.0.8 PASS All observations passed contract passed 3 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.

Recent failure clusters