@knapsack/storybook-adapter
Storybook Context Adapter
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Knapsack monorepo packages consistently lack provenance; stable false positive for this package family. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 4.93.0 | 4 / 7 | |
| 4.92.24 | 4 / 7 | |
| 4.92.23 | 4 / 7 | |
| 4.92.22 | 4 / 7 | |
| 4.92.21 | 4 / 7 | |
| 4.92.20 | 4 / 7 | |
| 4.92.19 | 4 / 7 | |
| 4.92.18 | 4 / 7 | |
| 4.92.17 | 4 / 7 | |
| 4.92.16 | 4 / 7 | |
| 4.92.15 | 4 / 7 | |
| 4.92.14 | 4 / 7 | |
| 4.92.13 | 4 / 7 | |
| 4.92.12 | 4 / 7 | |
| 4.92.11 | 4 / 7 | |
| 4.92.10 | 4 / 7 | |
| 4.92.9 | 4 / 7 | |
| 4.92.8 | 4 / 7 | |
| 4.92.7 | 4 / 7 | |
| 4.92.6 | 4 / 7 | |
| 4.92.5 | 4 / 7 | |
| 4.92.4 | 4 / 7 | |
| 4.92.3 | 4 / 7 | |
| 4.92.2 | 4 / 7 | |
| 4.92.1 | 4 / 7 | |
| 4.92.0 | 4 / 7 | |
| 4.91.0 | 4 / 7 | |
| 4.90.0 | 4 / 7 | |
| 4.89.13 | 4 / 7 | |
| 4.89.12 | 4 / 7 | |
| 4.89.11 | 4 / 7 |
v4.93.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.90.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.89.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.