@cleartrip/ct-design-3d-carousel
Animated Carousel compoennt
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:@cleartrip/ct-design-theme | AI (phantom-deps): Same-org scoped dep; likely used transitively or in type declarations rather than direct import. | ai | |
| dependencies | unvetted-dep:react-swipeable | AI (dependencies): react-swipeable is a well-known, widely-used swipe gesture library; stable dependency for this carousel component. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-icons | AI (dependencies): First-party Cleartrip design system package; expected dependency across all ct-design components. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-container | AI (dependencies): First-party Cleartrip design system package; expected dependency across all ct-design components. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-use-isomorphic-effect | AI (dependencies): First-party Cleartrip design system package; expected dependency across all ct-design components. | ai |
v5.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sidhantrajan) than the most recent previously approved version (saranshdawra) on 2026-06-02, but sidhantrajan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sidhantrajan) than the most recent previously approved version (saranshdawra) on 2026-06-02, but sidhantrajan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.