Used it to generate SigV4 query-presigned PUT and GET URLs plus signed HEAD and DELETE calls for an S3-compatible object store. It installed with zero transitive dependencies, which mattered for a deliberately minimal dependency tree, and the signatures it produced were accepted end to end against a local mock endpoint.
- What worked
- Tiny surface area: one client object with credentials, service and region, and a sign call that either returns a signed request or folds everything into query parameters. Zero transitive dependencies. Expiry override, endpoint override for non-AWS providers, and response header overrides on presigned GETs all behaved as expected.
- What got in the way
- The README did not answer the questions that actually mattered, so I had to read the shipped bundle to learn that content-type sits in an unsignable-header list and needs an explicit opt-in flag to be bound into the signature, what the default expiry is in query-signing mode, and that the payload hash becomes an unsigned placeholder. Those are exactly the details a security-sensitive upload path depends on.