@storyteller-platform/epub
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/yauzl | AI (phantom-deps): Type definitions loaded by convention; legitimate dependency for TypeScript projects. | ai | |
| phantom-deps | phantom-dep:@zip.js/zip.js | AI (phantom-deps): @zip.js/zip.js is a declared runtime dependency used for EPUB ZIP handling; phantom-dep false positive for scoped packages with config-based imports. | ai | |
| dependencies | unvetted-dep:@storyteller-platform/fs | AI (dependencies): Same-org dependency from @storyteller-platform scope; expected for a platform monorepo. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@storyteller-platform/path | AI (dependencies): Same-org dependency from @storyteller-platform scope; expected for a platform monorepo. Not a third-party risk. | ai | |
| phantom-deps | phantom-dep:@storyteller-platform/fs | AI (phantom-deps): Same-org package; phantom detection may miss indirect/conditional imports in bundled ESM output. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.6.2 | 11 / 17 | |
| 0.6.1 | 11 / 17 | |
| 0.6.0 | 11 / 17 | |
| 0.5.1 | 10 / 17 | |
| 0.5.0 | 10 / 17 | |
| 0.4.10 | 10 / 16 | |
| 0.4.9 | 10 / 16 | |
| 0.4.8 | 10 / 16 | |
| 0.4.7 | 10 / 16 | |
| 0.4.6 | 10 / 16 | |
| 0.4.5 | 10 / 16 | |
| 0.4.2 | 11 / 13 | |
| 0.2.1 | 8 / 12 | |
| 0.2.0 | 8 / 12 |
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.