@bymax-one/nest-storage 1.0.1 → 1.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/CHANGELOG.md +55 -1
  2. package/README.md +229 -77
  3. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -8,6 +8,58 @@ The format follows [Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/
8
8
 
9
9
  ## [Unreleased]
10
10
 
11
+ ## [1.0.3] - 2026-08-04
12
+
13
+ Documentation only. `dist/` is byte-identical to the one 1.0.2 published — verified by
14
+ unpacking `@bymax-one/nest-storage@1.0.2` from the registry and diffing it against a
15
+ fresh build (`diff -r`, no output), not asserted. 1.0.0 and 1.0.1 shipped the same
16
+ `dist/`, so the artifact has not changed since the first release.
17
+
18
+ ### Changed
19
+
20
+ - **The architecture diagram is drawn rather than listed.** Every published
21
+ `@bymax-one` library draws this section with box-drawing characters, laid out so the
22
+ picture shows what flows into what. This one had an indented tree of bullets with a
23
+ description beside each entry, which says what exists but not how a request moves
24
+ through it, which step feeds which, or where the decision is made. The redrawn
25
+ diagram carries what the prose underneath was saying alone: the single chokepoint
26
+ every caller-supplied key passes before it reaches S3, and the escape hatch beside
27
+ the two services rather than buried under them.
28
+
29
+ ## [1.0.2] - 2026-08-04
30
+
31
+ Documentation only, again — and for the same reason 1.0.1 existed: the README ships
32
+ inside the package, so a correction that stays on `main` leaves the npm page wrong.
33
+ `dist/` is byte-identical to 1.0.0 and 1.0.1, verified by unpacking the published
34
+ tarball and diffing it against a fresh build rather than asserting it.
35
+
36
+ ### Fixed
37
+
38
+ - **The vulnerability contact pointed at a mailbox that does not exist.** The README's
39
+ Security Policy and `SECURITY.md` both named `security@bymax.one`. A researcher
40
+ following those instructions sent a private disclosure into nothing — and from their
41
+ side, an unread inbox and a maintainer ignoring them look identical, so a report that
42
+ gets no acknowledgement is usually published anyway. Everything now names
43
+ `support@bymax.one`, the single inbox that routes.
44
+
45
+ ### Changed
46
+
47
+ - **The README follows the layout of the published `@bymax-one` libraries, not just
48
+ their section names.** The previous release standardized which sections exist and
49
+ left the inside of each as it was. Features is now grouped under subheadings with
50
+ one entry per capability, Overview carries a `Why nest-storage?` block, Architecture
51
+ carries the design-principles table that follows its diagram everywhere else,
52
+ Security Model is one subheading per property, and Testing & Quality states what the
53
+ suite is held to before listing the commands. The tail gained the family's license
54
+ line and footer, and Subpath Exports gained the dependency diagram and peer matrix.
55
+ - **Four statements corrected against the source.** `KeyResolverService` was listed as
56
+ public API and is not exported; the module was described as refusing an unusable
57
+ configuration at bootstrap, where `validate-options` deliberately tolerates empty
58
+ credentials so a development workflow boots; `STORAGE_INVALID_PART_COUNT` was missing
59
+ from the error table; and the suppression claim said the production source carries no
60
+ mutation directives, where it carries five, each naming why its mutant is provably
61
+ equivalent.
62
+
11
63
  ## [1.0.1] - 2026-08-03
12
64
 
13
65
  Documentation only. `dist/` is byte-identical to the one published in 1.0.0 —
@@ -134,4 +186,6 @@ have regressed from. They are kept because the reasoning is worth having.
134
186
 
135
187
  [1.0.0]: https://github.com/bymaxone/nest-storage/releases/tag/v1.0.0
136
188
  [1.0.1]: https://github.com/bymaxone/nest-storage/compare/v1.0.0...v1.0.1
137
- [Unreleased]: https://github.com/bymaxone/nest-storage/compare/v1.0.1...HEAD
189
+ [1.0.2]: https://github.com/bymaxone/nest-storage/compare/v1.0.1...v1.0.2
190
+ [1.0.3]: https://github.com/bymaxone/nest-storage/compare/v1.0.2...v1.0.3
191
+ [Unreleased]: https://github.com/bymaxone/nest-storage/compare/v1.0.3...HEAD
package/README.md CHANGED
@@ -33,21 +33,89 @@
33
33
 
34
34
  ## ✨ Overview
35
35
 
36
- `@bymax-one/nest-storage` is a NestJS dynamic module that wraps the AWS SDK v3 (`@aws-sdk/client-s3`) to provide a unified, provider-agnostic API for any S3-compatible object storage service. A single `StorageService` covers the full lifecycle — upload, download, signed URLs, listing, copy, and batch delete — while the pluggable `IUploadValidator` and `IFileScanner` hooks let you enforce your own MIME rules and virus-scan policies without coupling the library to any specific scanner.
36
+ `@bymax-one/nest-storage` is a NestJS dynamic module that wraps the AWS SDK v3
37
+ (`@aws-sdk/client-s3`) behind one typed surface for object storage. Instead of building an
38
+ `S3Client`, deciding per provider whether path-style addressing is required, and hand-rolling
39
+ multipart, presigning, validation and key normalization in every service, you install one
40
+ library and get all of it — against AWS S3, Cloudflare R2, Backblaze B2, DigitalOcean Spaces,
41
+ MinIO or Wasabi, with the same code.
42
+
43
+ The library has **zero direct dependencies** — the three `@aws-sdk/*` packages and `@nestjs/*`
44
+ arrive as peer dependencies, so you control exact versions and the supply-chain surface stays
45
+ minimal.
46
+
47
+ ### Why nest-storage?
48
+
49
+ - **One engine, six providers.** `providerRecipes` differ only in endpoint, region and the flags
50
+ each provider needs (`forcePathStyle` for MinIO, `auto` region for R2). There is no
51
+ per-provider code path, so switching provider is a configuration change and every operation
52
+ behaves the same way afterwards.
53
+ - **The key guard is one chokepoint.** Every caller-supplied key passes through
54
+ `KeyResolverService` before it reaches S3 — `..` segments, a leading `/`, null bytes and empty
55
+ keys are refused, and only then is `keyPrefix` prepended. A tenant cannot climb out of its
56
+ prefix by naming a key.
57
+ - **Uploads are refused before they are stored.** MIME allowlist and size limit first, then any
58
+ `IUploadValidator` you register, then the `IFileScanner` if configured — pre-upload,
59
+ post-upload, or both.
60
+ - **Presigned URLs cannot outlive what SigV4 allows.** TTLs are clamped and the hard ceiling of
61
+ 604 800 s is enforced locally, rather than handed to a signature the provider rejects at use
62
+ time.
63
+
64
+ ---
37
65
 
38
66
  ## 🔥 Features
39
67
 
40
- - **Multipart upload** via `@aws-sdk/lib-storage` with automatic abort on failure (`leavePartsOnError: false`), progress events, and a configurable part-size threshold
41
- - **Presigned GET / PUT / multipart URLs** with TTL clamping and a hard 7-day SigV4 ceiling
42
- - **MIME whitelist + size limit** (wildcards supported: `image/*`, `text/*`) with a pluggable `IUploadValidator` hook for magic-byte checks and custom business rules
43
- - **Pluggable `IFileScanner` hook** (pre- and/or post-upload) for ClamAV, AWS Macie, or any scanner that returns `'clean' | 'infected' | 'unknown'`
44
- - **Six ready-to-use provider recipes** — `awsS3`, `cloudflareR2`, `backblazeB2`, `digitalOceanSpaces`, `minio`, `wasabi`
45
- - **Path-traversal guard** in `KeyResolverService` — blocks `..`, leading `/`, and empty-after-normalize keys
46
- - **In-memory LRU idempotency cache** (default 1 000 entries / 24 h) — identical `idempotencyKey` returns the cached `UploadResult`
47
- - **Server-side encryption** (AES256 / aws:kms) configurable globally or per-upload
48
- - **`keyPrefix` multi-tenant isolation** — prepended to every resolved key
49
- - **`forRoot` / `forRootAsync`** dynamic module API; `@Global()` scope; `Symbol()` DI tokens
50
- - **`BYMAX_STORAGE_S3_CLIENT` token** for injecting the raw `S3Client` for provider-specific operations
68
+ ### ⬆️ Uploading
69
+
70
+ - ✅ **Multipart upload** — `@aws-sdk/lib-storage` with automatic abort on failure
71
+ (`leavePartsOnError: false`), progress events, and a configurable threshold and part size
72
+ - ✅ **Content validation** — MIME allowlist with wildcards (`image/*`, `text/*`) and a size
73
+ limit, refused before a byte is stored
74
+ - ✅ **Pluggable validators** — register any number of `IUploadValidator`s; each runs after the
75
+ built-in checks and can refuse with its own reason
76
+ - ✅ **Virus scanning hook** — `IFileScanner` pre-upload, post-upload or both, for ClamAV, AWS
77
+ Macie or anything that answers `'clean' | 'infected' | 'unknown'`
78
+ - ✅ **Idempotent retries** — an in-memory LRU (1 000 entries / 24 h by default) returns the
79
+ cached `UploadResult` for a repeated `idempotencyKey` instead of storing the object twice
80
+
81
+ ### 🔗 Access & URLs
82
+
83
+ - ✅ **Presigned GET / PUT** — with optional content-type and length conditions on the PUT
84
+ - ✅ **Presigned multipart** — one signed URL per part plus the upload id, so a browser can
85
+ upload directly without the bytes passing through your process
86
+ - ✅ **TTL clamping** — SigV4's hard ceiling of 604 800 s (7 days) is enforced locally, not
87
+ discovered when the provider rejects the signature
88
+ - ✅ **Public URL composition** — `getPublicUrl` builds from `cdnBaseUrl` or `publicBaseUrl` for
89
+ buckets that are public by policy; it composes, it does not sign
90
+
91
+ ### 🗄️ Objects & Lifecycle
92
+
93
+ - ✅ **Streaming download** — `download` returns a stream; the body is never buffered unless you
94
+ ask for `downloadBuffer`
95
+ - ✅ **Metadata without transfer** — `head` and `exists` answer from object metadata alone
96
+ - ✅ **Paginated listing** — `list` over continuation tokens, with the prefix stripped back off
97
+ the keys it returns
98
+ - ✅ **Server-side copy** — `copy` moves bytes inside the provider; they never reach this process
99
+ - ✅ **Bulk delete with partial results** — `deleteMany` reports what failed instead of throwing
100
+ away the successes
101
+
102
+ ### 🧩 Developer Experience
103
+
104
+ - ✅ **Six provider recipes** — `awsS3`, `cloudflareR2`, `backblazeB2`, `digitalOceanSpaces`,
105
+ `minio`, `wasabi`
106
+ - ✅ **Zero runtime dependencies** — `@aws-sdk/*` and `@nestjs/*` all arrive as peer
107
+ dependencies, so you pin the versions
108
+ - ✅ **Two subpaths** — the server surface, and `./shared` carrying types and the error catalog
109
+ that pull in nothing at all
110
+ - ✅ **Escape hatch** — `BYMAX_STORAGE_S3_CLIENT` injects the raw `S3Client` for the
111
+ provider-specific operations this surface deliberately does not wrap
112
+ - ✅ **Multi-tenant key prefix** — `keyPrefix` prepended after normalization, so it cannot be
113
+ escaped by the key
114
+ - ✅ **Server-side encryption** — AES256 or `aws:kms`, globally or per upload
115
+ - ✅ **Typed end to end** — TypeScript `strict` with `exactOptionalPropertyTypes` and
116
+ `noUncheckedIndexedAccess`; zero `any`
117
+
118
+ ---
51
119
 
52
120
  ## 📦 Subpath Exports
53
121
 
@@ -56,6 +124,29 @@
56
124
  | `.` | Server runtime: `BymaxStorageModule`, `StorageService`, `SignedUrlService`, `providerRecipes`, DI tokens, interfaces, `StorageException`, `NoOpUploadValidator`, `NoOpFileScanner` |
57
125
  | `./shared` | Framework-free types (`UploadResult`, `ObjectMetadata`, `ListedObject`, `SignedUrlResult`) + `STORAGE_ERROR_CODES` + `StorageErrorCode` |
58
126
 
127
+ ```
128
+ @bymax-one/nest-storage (server — NestJS + @aws-sdk/client-s3)
129
+ │
130
+ └── re-exports ──▶ @bymax-one/nest-storage/shared (zero dependencies)
131
+ ```
132
+
133
+ Both subpaths ship ESM **and** CommonJS with declarations for each format, so a
134
+ `require()` consumer receives CommonJS declarations rather than ESM ones. The
135
+ `pnpm check:exports` gate verifies this against the packed tarball.
136
+
137
+ ### Peer dependency matrix
138
+
139
+ | Subpath | Required peers |
140
+ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
141
+ | `.` (server) | `@nestjs/common ^11.0.16`, `@nestjs/core ^11.1.18`, `@aws-sdk/client-s3 ^3.700`, `@aws-sdk/lib-storage ^3.700`, `@aws-sdk/s3-request-presigner ^3.700`, `reflect-metadata ^0.2` |
142
+ | `./shared` | None |
143
+
144
+ ---
145
+
146
+ > [!TIP]
147
+ > A reference application lives in
148
+ > [`bymaxone/nest-storage-example`](https://github.com/bymaxone/nest-storage-example).
149
+
59
150
  ---
60
151
 
61
152
  ## 🚀 Quick Start
@@ -586,29 +677,39 @@ supply through it first: the guard below, then `keyPrefix`. The key you read bac
586
677
  ## 🏗️ Architecture
587
678
 
588
679
  ```
589
- BymaxStorageModule (@Global, forRoot / forRootAsync)
590
- │
591
- ├── validate-options ──────── refuses a malformed configuration at bootstrap.
592
- │ Credentials are the deliberate exception: empty
593
- │ values are tolerated so a dev workflow boots without
594
- │ storage, and operations then fail with
595
- │ STORAGE_NOT_CONFIGURED rather than at module load
596
- │
597
- ├── S3ClientProvider ───────── one @aws-sdk/client-s3 S3Client, built from the
598
- │ resolved provider recipe; exposed as
599
- │ BYMAX_STORAGE_S3_CLIENT for anything this surface
600
- │ deliberately does not wrap
601
- │
602
- ├── KeyResolverService ─────── the only place a caller-supplied key becomes an
603
- │ object key: guard, then keyPrefix
604
- │
605
- ├── StorageService ─────────── upload · download · head · exists · list · copy ·
606
- │ delete · deleteMany
607
- │ ├── IUploadValidator[] (MIME + size, then any you register)
608
- │ ├── IFileScanner (pre- and/or post-upload)
609
- │ └── IdempotencyCache (LRU, in-process)
610
- │
611
- └── SignedUrlService ───────── GET / PUT / multipart presigns, TTL-clamped
680
+ BymaxStorageModule.forRoot / forRootAsync
681
+ │
682
+ validateOptions (fail fast)
683
+ credentials tolerated empty on purpose
684
+ │
685
+ ┌───────────────┴────────────────┐
686
+ │ S3ClientProvider │
687
+ │ one @aws-sdk/client-s3 client │
688
+ │ built from a provider recipe │
689
+ └───────────────┬────────────────┘
690
+ │
691
+ BYMAX_STORAGE_S3_CLIENT
692
+ (escape hatch — the raw S3Client)
693
+ │
694
+ ┌─────────────────────────┴─────────────────────────┐
695
+ │ │
696
+ StorageService SignedUrlService
697
+ upload · download GET · PUT · multipart
698
+ head · exists · list TTL-clamped
699
+ copy · delete · deleteMany SigV4 ceiling 7 days
700
+ │ │
701
+ └──────────────┬────────────────────────────────────┘
702
+ │
703
+ KeyResolverService
704
+ every caller key passes here before S3:
705
+ refuse `..`, leading `/`, NUL, empty → then keyPrefix
706
+ │
707
+ ┌────────────────────┼────────────────────┐
708
+ │ │ │
709
+ IUploadValidator[] IFileScanner IdempotencyCache
710
+ MIME + size, then pre- and/or LRU, in-process,
711
+ yours post-upload collapses a retry
712
+ (yours) (yours) within one instance
612
713
  ```
613
714
 
614
715
  One engine, six recipes. `providerRecipes` differ only in endpoint, region and the
@@ -619,35 +720,66 @@ change and every operation behaves the same way afterwards.
619
720
  The idempotency cache is **in-process**. It collapses a retried `upload` inside one
620
721
  instance; it does not coordinate between replicas.
621
722
 
723
+ ### Design Principles
724
+
725
+ | Principle | Description |
726
+ | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
727
+ | 🔑 **One key chokepoint** | Every caller-supplied key passes through `KeyResolverService` before it reaches S3. `..`, a leading `/`, null bytes and empty keys are refused, and `keyPrefix` is prepended after normalization — so it cannot be escaped by the key |
728
+ | 🧩 **One engine, six recipes** | `providerRecipes` differ in endpoint, region and per-provider flags only. There is no per-provider code path, so a provider swap is configuration and every operation behaves the same afterwards |
729
+ | 🚫 **Refuse before storing** | MIME allowlist and size limit, then registered `IUploadValidator`s, then the `IFileScanner`. An upload that will be rejected is rejected before a byte is written |
730
+ | ⏱️ **Bounded signatures** | Presign TTLs are clamped and SigV4's 604 800 s ceiling is enforced locally, not discovered when the provider rejects the signature |
731
+ | 💥 **Fail at boot, mostly** | Options are validated before any client is built. Credentials are the deliberate exception: empty values are tolerated so a development workflow boots, and operations then fail with `STORAGE_NOT_CONFIGURED` |
732
+ | 🧊 **Zero runtime dependencies** | `dependencies` is `{}`. You choose the exact `@aws-sdk/*` versions and the supply-chain surface stays yours |
733
+
622
734
  ---
623
735
 
624
736
  ## 🔐 Security Model
625
737
 
626
- **The object key is the attack surface.** Everything a caller sends becomes part of a
627
- key, and a key is a path. `KeyResolverService.normalize` is the single chokepoint:
628
- it refuses an empty key, a key containing a null byte, a key starting with `/`, and
629
- any key with a `..` segment; it collapses duplicate slashes; and only then does it
630
- prepend `keyPrefix`. Nothing in this library composes a key any other way, so a
631
- tenant cannot climb out of its prefix by naming one.
632
-
633
- **Presigned URLs are bearer credentials.** Anyone holding one has the access it
634
- encodes, for as long as it lives. TTLs are clamped, and SigV4's hard ceiling of
635
- 604 800 s (7 days) is enforced rather than passed through to a signature the provider
636
- would reject at use time.
637
-
638
- **Credentials stay where they were put.** They arrive through module options and are
639
- handed to the SDK. This library never reads `process.env`, never logs them, and never
640
- places them — or a signed URL — in an exception. What `aws-error-mapper` does put in
641
- `details` is the provider's error code and message, the HTTP status, the request id,
642
- and the operation context the call site supplies: which operation, which bucket, and
643
- the resolved key or prefix. That is enough to diagnose a failure, and it means an
644
- object key reaches whatever consumes the exception — so if a key is itself sensitive
645
- in your deployment, do not log the envelope verbatim.
646
-
647
- **Uploads are refused before they are stored, not after.** MIME allowlist (wildcards
648
- included) and size limit run first, then any `IUploadValidator` you register, then the
649
- `IFileScanner` if configured. A scanner can run pre-upload, post-upload, or both — the
650
- post-upload position exists because some scanners only accept an object they can fetch.
738
+ This library turns caller input into object keys, signs URLs that grant access on their
739
+ own, and holds the credentials for a bucket. Its security contract is about what a key can
740
+ reach, how long a signature lives, and what leaves in an error.
741
+
742
+ ### The object key is the attack surface
743
+
744
+ Everything a caller sends becomes part of a key, and a key is a path.
745
+ `KeyResolverService.normalize` is the single chokepoint: it refuses an empty key, a key
746
+ containing a null byte, a key starting with `/`, and any key with a `..` segment; it
747
+ collapses duplicate slashes; and only then does it prepend `keyPrefix`. Nothing in this
748
+ library composes a key any other way, so a tenant cannot climb out of its prefix by naming
749
+ one.
750
+
751
+ ### Presigned URLs are bearer credentials
752
+
753
+ Anyone holding one has the access it encodes, for as long as it lives. TTLs are clamped,
754
+ and SigV4's hard ceiling of 604 800 s (7 days) is enforced here rather than passed through
755
+ to a signature the provider would reject at use time. Treat a signed URL like a password
756
+ with an expiry, not like a link.
757
+
758
+ ### Credentials stay where they were put
759
+
760
+ They arrive through module options and are handed to the SDK. This library never reads
761
+ `process.env`, never logs them, and never places them — or a signed URL — in an exception.
762
+
763
+ ### Error payloads carry the operation, and that includes the key
764
+
765
+ What `aws-error-mapper` puts in `details` is the provider's error code and message, the
766
+ HTTP status, the request id, and the operation context the call site supplies: which
767
+ operation, which bucket, and the resolved key or prefix. That is enough to diagnose a
768
+ failure, and it means an object key reaches whatever consumes the exception — so if a key
769
+ is itself sensitive in your deployment, do not log the envelope verbatim.
770
+
771
+ ### Uploads are refused before they are stored
772
+
773
+ MIME allowlist (wildcards included) and size limit run first, then any `IUploadValidator`
774
+ you register, then the `IFileScanner` if configured. A scanner can run pre-upload,
775
+ post-upload, or both — the post-upload position exists because some scanners only accept an
776
+ object they can fetch.
777
+
778
+ ### `keyPrefix` is a namespace, not an access boundary
779
+
780
+ It scopes the keys this library composes; it does not restrict what the credentials can
781
+ reach. Anything holding the bucket's credentials can read every prefix in it. Isolation
782
+ that must survive a compromised client belongs in IAM policies or separate buckets.
651
783
 
652
784
  ---
653
785
 
@@ -687,37 +819,57 @@ post-upload position exists because some scanners only accept an object they can
687
819
 
688
820
  ## 🧪 Testing & Quality
689
821
 
690
- ```bash
691
- # Unit tests
692
- pnpm test
693
-
694
- # Unit tests with coverage (100% threshold enforced)
695
- pnpm test:cov
696
-
697
- # E2E tests (requires Docker — spins MinIO via Testcontainers)
698
- pnpm test:e2e
822
+ Object storage is where a bug is expensive to discover later — a key written to the wrong
823
+ place stays there — so the suite is held to a bar beyond "the tests pass".
824
+
825
+ - ✅ **100% line coverage** — statements, branches, functions and lines, enforced as a gate
826
+ - ✅ **100% mutation score** — verified with [Stryker](https://stryker-mutator.io/) at
827
+ `break: 95`; every survivor was killed by a strengthened assertion, and the eight provable
828
+ equivalents are documented inline
829
+ - ✅ **Real object storage in e2e** — MinIO through Testcontainers, so multipart, presigning
830
+ and listing are exercised against an actual S3 API rather than a mock
831
+ - ✅ **Published-artifact gates** — `check:exports` resolves the types the way each module
832
+ system does, `check:runtime` loads every subpath from the packed tarball in ESM and
833
+ CommonJS, and `check:published` compiles this README's snippets against `dist/`
834
+ - ✅ **Every suppression is justified** — no coverage directives anywhere; the five
835
+ `// Stryker disable` comments in the production source each name why the mutant they
836
+ silence is provably equivalent, and the mutation report lists them
699
837
 
700
- # Mutation testing (Stryker — run manually pre-release, not on every CI commit)
701
- pnpm mutation
838
+ ```bash
839
+ pnpm test # unit tests (Jest)
840
+ pnpm test:cov # unit tests with the 100% coverage gate
841
+ pnpm test:e2e # end-to-end against MinIO (requires Docker)
842
+ pnpm mutation # Stryker mutation testing (break: 95)
843
+ pnpm typecheck # tsc strict check
844
+ pnpm lint # ESLint
702
845
  ```
703
846
 
704
847
  ---
705
848
 
706
849
  ## 🤝 Contributing
707
850
 
708
- For feature requests and bugs, open a GitHub issue. Pull requests are welcome; please run `pnpm test:cov` and `pnpm lint` before submitting.
851
+ Pull requests are welcome. Please open an issue first for significant changes.
852
+
853
+ - Read [`docs/technical_specification.md`](docs/technical_specification.md) for architecture decisions.
854
+ - Run `pnpm test:cov` and `pnpm lint` before opening a PR.
855
+ - Please use Conventional Commits for the message; nothing enforces it here, so it is a convention rather than a gate.
709
856
 
710
857
  ---
711
858
 
712
859
  ## 🔒 Security Policy
713
860
 
714
- If you discover a security vulnerability, please **do not** open a public issue.
715
- Instead, email us at **security@bymax.one** with details. We take security seriously
716
- and will respond promptly. See [`SECURITY.md`](SECURITY.md) for the full policy,
717
- including the storage-specific security goals.
861
+ If you discover a security vulnerability, please **do not** open a public issue. Instead, email us
862
+ at **support@bymax.one** with details. We take security seriously and will respond promptly. See
863
+ [`SECURITY.md`](SECURITY.md) for the full policy, including the storage-specific security goals.
718
864
 
719
865
  ---
720
866
 
721
867
  ## 📄 License
722
868
 
723
- [MIT](LICENSE) — Copyright (c) 2026 Bymax One
869
+ [MIT](./LICENSE) © [Bymax One](https://github.com/bymaxone)
870
+
871
+ ---
872
+
873
+ <p align="center">
874
+ <sub>Built with ❤️ by <a href="https://github.com/bymaxone">Bymax One</a></sub>
875
+ </p>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@bymax-one/nest-storage",
3
- "version": "1.0.1",
3
+ "version": "1.0.3",
4
4
  "description": "Provider-agnostic S3-compatible object storage for NestJS. Works with AWS S3, DigitalOcean Spaces, Cloudflare R2, Backblaze B2, MinIO, Wasabi.",
5
5
  "author": "Bymax One <support@bymax.one>",
6
6
  "license": "MIT",