@blamejs/pki 0.5.9 → 0.5.11

package/lib/guard-compress.js

@@ -22,7 +22,7 @@
 //     unboundedly many encodings, and a digest over the compressed object would
 //     stop identifying what it decompresses to.
 //
-// Both defences are applied here, once, for every algorithm, so a new consumer
+// Both defenses are applied here, once, for every algorithm, so a new consumer
 // cannot pick up one and miss the other. Verified uniform across zlib, brotli
 // and zstd: each reports consumed input as `engine.bytesWritten` under
 // `info: true`, each raises ERR_BUFFER_TOO_LARGE on a cap breach, and each
@@ -125,7 +125,7 @@ function bounded(algorithm, stream, cap, E, codes, label) {
     throw new TypeError("guard.compress.bounded: stream must be a Buffer (route the input through guard.bytes.view first)");
   }
   // The ceiling is an authoring input: an undefined / NaN / fractional / negative
-  // cap would silently disable the bomb defence. It must also be at least 1 --
+  // cap would silently disable the bomb defense. It must also be at least 1 --
   // node rejects maxOutputLength 0 with a different fault than a cap breach, so a
   // zero cap would surface as a malformed-stream verdict instead of a config error.
   if (!Number.isInteger(cap) || cap < 1) {

package/lib/guard-der.js

@@ -26,7 +26,7 @@
 // Every entry point takes the CALLER's error factory and code, so a c509 splice reports in
 // the c509 domain and a certificate builder in the x509 domain.
 // asn1-der composes this guard family, so requiring the codec at module scope would read its
-// exports mid-initialisation and see an empty object. The require and the table it builds are
+// exports mid-initialization and see an empty object. The require and the table it builds are
 // therefore both deferred to first use -- the documented circular-load exception to top-of-file
 // requires. Guards sit BELOW the codec in the dependency order; this is the one place that
 // order is inverted, and it is inverted lazily.