Recordsnpm@smithy/signature-v45.7.3
Change the conditions
Current conditions
@smithy/signature-v4 @5.7.3windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
0 of 3 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
- 39 / 44
- Contract verifications
- 0 / 3
- Usage records
- 12
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Evidence you can open
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @smithy/core | 3.33.3 | contract passed | 2 project-days |
| @smithy/types | 4.17.2 | contract passed | 2 project-days |
| tslib | 2.8.1 | contract passed | 2 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 | 5.7.3 | 5.3.8 |
|---|---|---|
| @smithy/types | 4.17.2 | 4.12.0 |
| @smithy/core | 3.33.3 | — |
| @smithy/is-array-buffer | — | 4.2.0 |
| @smithy/protocol-http | — | 5.3.8 |
| @smithy/util-hex-encoding | — | 4.2.0 |
| @smithy/util-middleware | — | 4.2.8 |
| @smithy/util-uri-escape | — | 4.2.0 |
| @smithy/util-utf8 | — | 4.2.0 |
| tslib | 2.8.1 | 2.8.1 |
Moved: 1 · unchanged at every release: 8
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
-
observed PROJECT_TEST exit 1 ×1 5.7.3 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:0ae8b1ca283c…expected: <path><str><path> · operator: <str>, · diff: <str> · }javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 5.7.3 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:4904e63e5296…AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · + actual - expected · + <str> · - <str>javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 5.7.3 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:58e107af7157…AssertionError [ERR_ASSERTION]: inventory that nobody paid for does not make the publisher share rise · at TestContext.<anonymous> (<url>) …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 5.7.3 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:7b58f94a4bfb…AssertionError [ERR_ASSERTION]: The input did not match the regular expression <path> 사이트에서 유효 노출 1회/. Input: · <str> …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 5.7.3 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:cad2d38151f2…AssertionError [ERR_ASSERTION]: The input did not match the regular expression <path><str><path> Input: · <str> + · <str> + · <str> +javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 5.7.3 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:0e6d2b674efc…✔ defaults to something the process can reach itself (0.4995ms) …npm · unclassified-diagnostic · outer npm run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 5.7.3 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:b1efc22a8950…✔ client address (2.476ms) · ▶ published public origin · ✔ defaults to something the process can reach itself (0.5926ms) …npm · unclassified-diagnostic · outer npm run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 5.7.3 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:d98d3e870785…<str> + · <str> + · <str> + · <str> +npm · unclassified-diagnostic · outer npm run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01Diagnostic re-verification candidate