@storyteller-platform/align MIT 16 versions

@storyteller-platform/align

npm Repository

A library and CLI for automatically aligning audiobooks and EPUBs to produce Media Overlays

16

Versions

MIT

License

Yes

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

smoores

Keywords

epubebookspeech-to-textaudiobook

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	bundled-binaries	AI (npm-metadata): Prebuilt .node binaries are expected for this native addon package using prebuildify.	ai	2026/04/27
provenance	publisher-changed	AI (provenance): Publisher changed to GitLab CI/CD matching the package's own GitLab repo org — consistent with CI/CD automation adoption.	ai	2026/04/27
phantom-deps	phantom-dep:@echogarden/icu-segmentation-wasm	AI (phantom-deps): Platform-specific WASM binary dependency; dynamic loading without direct import is the standard pattern for such packages.	ai	2026/04/27
phantom-deps	phantom-dep:zod	AI (phantom-deps): Schema validation library commonly referenced in config files; indirect usage pattern is expected for this package type.	ai	2026/04/27
phantom-deps	phantom-dep:chalk	AI (phantom-deps): CLI output library; may be used indirectly through CLI tooling or config. Consistent with this package's CLI functionality.	ai	2026/04/27
phantom-deps	phantom-dep:esbuild	AI (phantom-deps): esbuild is explicitly invoked in the compile script and used as a bundler; its indirect import pattern is expected for build tooling in this package.	ai	2026/04/27
install-scripts	install-script:install	AI (install-scripts): node-gyp-build is the standard install script for native Node.js addons with prebuilt binaries. Package has node-gyp, node-addon-api, and prebuildify as devDeps confirming legitimate native addon use.	ai	2026/04/26

Versions (showing 16 of 16)

Version	Deps	Published
0.1.41	27 / 13	2026-05-25
0.1.27	22 / 12	2026-04-11
0.1.18	21 / 12	2026-03-30
0.1.16	21 / 12	2026-03-30
0.1.15	21 / 12	2026-03-29
0.1.11	21 / 12	2026-03-24
0.1.10	21 / 12	2026-03-23
0.1.9	18 / 9	2026-03-15
0.1.8	18 / 9	2026-03-14
0.1.7	18 / 9	2026-03-13
0.1.6	15 / 9	2026-03-05
0.1.4	15 / 9	2026-03-05
0.1.2	15 / 9	2026-03-05
0.1.1	15 / 9	2026-03-05
0.1.0	15 / 9	2026-03-05
0.0.1	15 / 9	2026-03-05

v0.1.41

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.18

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/@storyteller-platform+align.node • prebuilds/linux-arm64/@storyteller-platform+align.node • prebuilds/linux-x64/@storyteller-platform+align.node

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.16

2 findings

HIGH Package has 'install' script install-scripts

Script: node-gyp-build

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.15

2 findings

HIGH Package has 'install' script install-scripts

Script: node-gyp-build

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.