@storyteller-platform/fs
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal platform utility package; sparse metadata is expected for org-scoped tooling, not a spam/malware indicator. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @storyteller-platform/fs has no naming, branding, or functional relationship to 'qs'. Levenshtein match is a false positive on the short suffix 'fs' vs 'qs'. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @storyteller-platform/fs has no naming, branding, or functional relationship to 'pg'. Edit-distance match is coincidental and not a credible typosquat vector. | ai |
v0.1.4
2 findingsPackage name '@storyteller-platform/fs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.