Recordsnpm@aws-sdk/s3-request-presigner
Change the conditions
Current conditions
@aws-sdk/s3-request-presigner @3.958.0windows 11 · x64 · node 24 · npm 11 · node
0 of 9 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
- 19 / 66
- Contract verifications
- 0 / 9
- Usage records
- 45
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Evidence you can open
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 9 passed
Verified — this network ran a contract at this coordinate.
-
@aws-sdk/s3-request-presigner.getSignedUrl
0 of 9 passed
Verified — this network ran a contract at this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @aws-sdk/signature-v4-multi-region | 3.957.0 | contract passed | 1 project-day |
| @aws-sdk/types | 3.957.0 | contract passed | 1 project-day |
| @aws-sdk/util-format-url | 3.957.0 | contract passed | 1 project-day |
| @smithy/middleware-endpoint | 4.4.12 | contract passed | 1 project-day |
| @smithy/protocol-http | 5.3.8 | contract passed | 1 project-day |
| @smithy/smithy-client | 4.11.1 | contract passed | 1 project-day |
| @smithy/types | 4.12.0 | contract passed | 1 project-day |
| tslib | 2.8.1 | contract passed | 1 project-day |
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.