@jscrypto/speck

Migration Notice

@jscrypto/speck is a legacy standalone package. It remains installable with @jscrypto/core up to 0.9.1, but new integrations should use the component package listed below.

Starting with @jscrypto 0.9.0, SPECK components moved into the new component architecture:

• Node / bundlers: use @jscrypto/ciphers
• Browser bundle: use @jscrypto/ciphers/speck/browser
• Registry preset: use speckPreset from @jscrypto/ciphers/speck

This package now declares @jscrypto/core as >=0.8.0 <=0.9.1 for compatibility with transition releases. Prefer the new @jscrypto/ciphers component layout for 0.9.x projects.

SPECK block cipher components for @jscrypto/core.

This package is an adapter. It depends on js-speck for the SPECK algorithm and registers each SPECK variant as a fixed-size @jscrypto block cipher component.

SPECK is a niche/legacy/lightweight block cipher family. Do not treat it as a default recommendation for new encryption designs.

The raw SPECK component has no mode, padding, IV, KDF, salt, or authentication by itself. If a protocol specifically requires modes or paddings, compose them from @jscrypto/classic. Modes can be composed only when their structural requirements are met; for example, GCM requires a 128-bit block cipher, so only SPECK128 variants are structurally compatible.

Demo

Speck Encrypt Online
Speck Decrypt Online

Install

npm install @jscrypto/speck

Optional modes and paddings:

npm install @jscrypto/classic

Quick Start

import { registry } from '@jscrypto/classic';
import { speckPreset } from '@jscrypto/speck';

registry.use(speckPreset);

const cipher = registry.createCipher({
  cipher: 'SPECK64/128',
  mode: 'CBC',
  padding: 'Pkcs7',
  key,
  iv,
});

Direct Helper

import { createSpeckCipher } from '@jscrypto/speck';

const cipher = createSpeckCipher('64-128', key);
const output = new Uint8Array(plaintextBlock.length);
cipher.encrypt(plaintextBlock, output);

There is no default variant. Always pass an explicit helper name such as 64-128.

Requires @jscrypto/core v0.8.0 or later.

Variants

| Helper | Registry name | Block | Key | |----------|-----------------|-------|------| | 32-64 | SPECK32/64 | 4 | 8 | | 48-72 | SPECK48/72 | 6 | 9 | | 48-96 | SPECK48/96 | 6 | 12 | | 64-96 | SPECK64/96 | 8 | 12 | | 64-128 | SPECK64/128 | 8 | 16 | | 96-96 | SPECK96/96 | 12 | 12 | | 96-144 | SPECK96/144 | 12 | 18 | | 128-128| SPECK128/128 | 16 | 16 | | 128-192| SPECK128/192 | 16 | 24 | | 128-256| SPECK128/256 | 16 | 32 |

Key length alone is not enough to choose a variant. For example, 12-byte keys are shared by Speck48/96, Speck64/96, and Speck96/96.

Browser

Browser builds are split by package. Load @jscrypto/core and @jscrypto/classic when you need a registry with modes or paddings, then register the SPECK preset from @jscrypto/speck.

<script src="jscrypto-core.iife.min.js"></script>
<script src="jscrypto-classic.iife.min.js"></script>
<script src="jscrypto-speck.iife.min.js"></script>
<script>
  jscryptoClassic.registry.use(jscryptoSpeck.speckPreset);
</script>

Package export paths:

• @jscrypto/speck/browser
• @jscrypto/speck/umd

UMD/AMD builds expose SPECK components and do not re-export @jscrypto/core. Load @jscrypto/core or @jscrypto/classic separately when you need a registry.

CommonJS users can require the regular UMD .js builds because this package uses explicit .mjs and .cjs entry files instead of package-level "type": "module".

License

MIT