@storyteller-platform/ghost-story
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is explicitly listed as a runtime dependency in package.json; the phantom-dep heuristic is a false positive here — it is used in CLI/build code. | ai | |
| dependencies | unvetted-dep:@aws-sdk/client-transcribe-streaming | AI (dependencies): AWS SDK for Transcribe Streaming is a well-known, legitimate AWS package; its use is expected in a speech/transcription toolset. | ai | |
| dependencies | unvetted-dep:ffmpeg-stream | AI (dependencies): ffmpeg-stream is a well-known ffmpeg wrapper; its use is appropriate for a speech/audio processing library. | ai | |
| dependencies | unvetted-dep:@robingenz/zli | AI (dependencies): CLI utility library appropriate for a tool with a bin entry; no security concerns. | ai | |
| dependencies | unvetted-dep:@aws-sdk/client-transcribe | AI (dependencies): Official AWS SDK for Amazon Transcribe; expected dependency for a speech-to-text toolset. | ai | |
| dependencies | unvetted-dep:microsoft-cognitiveservices-speech-sdk | AI (dependencies): Official Microsoft Azure Cognitive Services Speech SDK; expected dependency for a speech-to-text toolset. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.1.11 | 13 / 12 | |
| 0.1.10 | 13 / 12 | |
| 0.1.9 | 13 / 12 | |
| 0.1.8 | 13 / 12 | |
| 0.1.7 | 13 / 12 | |
| 0.1.6 | 13 / 12 | |
| 0.1.5 | 13 / 12 | |
| 0.1.4 | 12 / 12 | |
| 0.1.3 | 12 / 12 | |
| 0.1.2 | 12 / 12 | |
| 0.1.1 | 12 / 12 | |
| 0.1.0 | 12 / 12 | |
| 0.0.1 | 10 / 11 |
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.