@plasmicpkgs/react-slick
Plasmic registration call for the React Slick Slider component
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:slick-carousel | AI (phantom-deps): Declared as runtime dependency; phantom-dep heuristic is false positive for wrapper packages. | ai | |
| phantom-deps | phantom-dep:@seznam/compose-react-refs | AI (phantom-deps): Declared as runtime dependency; phantom-dep heuristic is false positive for wrapper packages. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.0.268 | 3 / 6 | |
| 0.0.267 | 3 / 6 | |
| 0.0.266 | 3 / 6 | |
| 0.0.265 | 3 / 6 | |
| 0.0.264 | 3 / 6 | |
| 0.0.263 | 3 / 6 | |
| 0.0.262 | 3 / 6 | |
| 0.0.261 | 3 / 6 | |
| 0.0.260 | 3 / 6 | |
| 0.0.259 | 3 / 6 | |
| 0.0.258 | 3 / 6 | |
| 0.0.257 | 3 / 6 | |
| 0.0.256 | 3 / 6 | |
| 0.0.255 | 3 / 6 | |
| 0.0.254 | 3 / 6 | |
| 0.0.253 | 3 / 6 | |
| 0.0.252 | 3 / 6 | |
| 0.0.251 | 3 / 6 | |
| 0.0.250 | 3 / 6 | |
| 0.0.249 | 3 / 6 | |
| 0.0.248 | 3 / 6 | |
| 0.0.247 | 3 / 6 | |
| 0.0.246 | 3 / 8 | |
| 0.0.245 | 3 / 8 | |
| 0.0.244 | 3 / 8 | |
| 0.0.243 | 3 / 8 | |
| 0.0.242 | 3 / 8 | |
| 0.0.241 | 3 / 8 | |
| 0.0.240 | 3 / 8 | |
| 0.0.239 | 3 / 8 | |
| 0.0.238 | 3 / 8 |
v0.0.268
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.267
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.266
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.265
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.264
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.263
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.262
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.261
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.260
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.259
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.258
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.257
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.256
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.255
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.254
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.253
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.251
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.250
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.249
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.248
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.247
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.246
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.245
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.244
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.239
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.238
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.